Am Donnerstag, 27. Juni 2002 23:41 schrieb David Brownell:
> Oliver Neukum wrote:
> > Am Donnerstag, 27. Juni 2002 21:33 schrieben Sie:
> >>OK, I'll let you fix that BKL stuff (didn't you add it
> >>in the first place? :) but this looks like the locking
> >
> > I did not add it. It was there for a
About the BKL stuffs...
As I can see on linux-2.5.22 no BKL is needed.
The idea is just to use __MOD_INC_USE_COUNT and __MOD_DEC_USE_COUNT, though I have the
feeling that there should be at least a minimum locking mechanism to guide safe
"driver->owner".
Is this idea also applicable on 2.4 or
Hello,
first: I run an Embedded Linux system, so Kernel 2.4.18 shouldn't be changed
by now.
I connect one usb printer and open a usb printer device "/dev/usblp0" and do
some writing into this file. The printer works, but sometimes I get a -1 as
a return from a write call. Then the printer stucks
Hello David,
Thanks for your response
Actually what I am trying to do in demo project is put the Linux code in an
embedded environment to support only a printer and a mass storage
device.(no multiple interfaces) connected to root hub. so I wanted to know
whether all the below things like bus s
