usb net1080.c vendor/device id

in kernel 2.4.3 2.4.4 2.4.5 In drivers/usb/net1080.c somewhere near line 61 i see the following { USB_DEVICE(0x1080, 0x525), the vendor and device id are reversed. I have changed this to { USB_DEVICE(0x525, 0x1080), and it worked since then. I have checked it against the id d

Re: ReiserFS? How reliable is it? Is this the future?

I use reiserfs on a) P3(450) machine 440BX/ZX Chipset 82371AB PIIX4 IDE UDMA33 b) athlon(1100) VIA KT133 something IDE UDMA33 On both of them i have spurious small file garbage problems during compiling. There was no situation with real trouble, no permanent damage, restarting the job solved the

Re: ES1371 driver in kernel 2.4.2

I am facing the same trouble but in my case the parallel printer driver complains about a possible interrupt sharing problem because i run it on interrupt 7. The alsa driver however works pretty well with this chip for me. The sound chip does not generate any interrupts on its own line. So it do

Re: Signal handling different for root and others

Andi Kleen wrote: > > On Tue, Sep 12, 2000 at 11:33:31AM +0100, Alan Cox wrote: > > > > Normal users are only able to create a SIGIO signal when connecting. > > > > > > That's very unlikely. TCP does not propagate gid/uid information over sockets, > > > not even over localhost. > > > > However if

Re: Signal handling different for root and others

Andi Kleen wrote: > > On Tue, Sep 12, 2000 at 02:20:02AM +0200, jury gerold wrote: > > I ran into a problem with 2.2.x kernels, posix signals and sockets. > > > > I have a program that creates a serversocket, puts it into listen state, > > attaches the socket t

Signal handling different for root and others

I ran into a problem with 2.2.x kernels, posix signals and sockets. I have a program that creates a serversocket, puts it into listen state, attaches the socket to a realtime signal and simply waits for the signal. When i create a connection (telnet a.b.c.d port) the signal is delivered dependin