On Wed, Oct 6, 2010 at 6:09 PM, Thomas Klose <thomas.klose@xxxxxxxxxxxxx> wrote:
>> > If for some reason the user explicitly does not want the system to load
>> > a certain module, he can create an blacklist entry in /etc/modprobe.d
>>
>> This is one way, but not the only way. Last time it might be the only
>> way, now it is not.
>
> That is not the question. The real issue is: Should a library like
> libftdi by default tamper with the system's global configuration?
>
You talked about "global configuration". What do you mean by that?
You use libftdi with a specific goal. And to achieve that goal,
you have to use libusb. In order to use libusb, you have to detach
the kernel driver. Period. If you do not like this behavior, then
do not use libusb or libftdi.
There are many projects under Linux which use libusb. They
are doing the same things in terms of driver detaching.
I really do not understand what you are trying to achieve here.
--
Xiaofan
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
|
