RE: For comment: draft BIOS use document for the kernel

Looks somewhat familiar. 8;) (compare http://rddunlap.home.att.net/linit/lin240_init_x86.html) (blatant plug) Some comments below. > -Original Message- > From: Alan Cox [mailto:[EMAIL PROTECTED]] > Linux 2.4 BIOS usage reference > > > Boot Sequence > - > ... > > int

RE: For comment: draft BIOS use document for the kernel

Looks somewhat familiar. 8;) (compare http://rddunlap.home.att.net/linit/lin240_init_x86.html) (blatant plug) Some comments below. -Original Message- From: Alan Cox [mailto:[EMAIL PROTECTED]] Linux 2.4 BIOS usage reference Boot Sequence - ... int 0x10

RE: Undocumented configuration symbols in 2.4.6pre2

Hi, Could you make these 5 instances of "Not unsure" be more palatable and less confusing? E.g., "Not sure" or "If not sure". But not the double negative... As is, it basically says: "Sure ? say M." ~Randy > -Original Message- > From: Maksim Krasnyanskiy [mailto:[EMAIL PROTECTED]] >

RE: Undocumented configuration symbols in 2.4.6pre2

Hi, Could you make these 5 instances of Not unsure be more palatable and less confusing? E.g., Not sure or If not sure. But not the double negative... As is, it basically says: Sure ? say M. ~Randy -Original Message- From: Maksim Krasnyanskiy [mailto:[EMAIL PROTECTED]]

RE: Kernel 2.4.x TODO

> From: Sasi Peter [mailto:[EMAIL PROTECTED]] > > > Check out the kernel janitor project at > > http://bazar.conectiva.com.br/~acme/TODO (original) > > Is this information up2date? If it is, sad to see we have > this many bugs... "Last updated in: Mon Feb 26 21:19:49 EST 2001" The other

RE: Kernel 2.4.x TODO

From: Sasi Peter [mailto:[EMAIL PROTECTED]] Check out the kernel janitor project at http://bazar.conectiva.com.br/~acme/TODO (original) Is this information up2date? If it is, sad to see we have this many bugs... "Last updated in: Mon Feb 26 21:19:49 EST 2001" The other link that I

RE: ac15 and 2.4.5-pre6, pwc format conversion

> From: Erik Mouw [mailto:[EMAIL PROTECTED]] > > On Fri, May 25, 2001 at 10:48:12AM +0200, Nemosoft Unv. wrote: > > On 25-May-01 Norbert Preining wrote: > > > According to ac ChangeLog: > > > o Rip format conversion out of the pwc driver (me) > > > | It belongs in user space..

RE: changes betwwen 2.2 | 2.4

See http://www.firstfloor.org/~andi/softnet/ ~Randy --- > From: sebastien person [mailto:[EMAIL PROTECTED]] > > Is there any documents that explain how upgrade network > driver from 2.2. to 2.4.? that gives details on changes ... > > Or maybe best

RE: changes betwwen 2.2 | 2.4

See http://www.firstfloor.org/~andi/softnet/ ~Randy --- From: sebastien person [mailto:[EMAIL PROTECTED]] Is there any documents that explain how upgrade network driver from 2.2. to 2.4.? that gives details on changes ... Or maybe best way is

RE: ac15 and 2.4.5-pre6, pwc format conversion

From: Erik Mouw [mailto:[EMAIL PROTECTED]] On Fri, May 25, 2001 at 10:48:12AM +0200, Nemosoft Unv. wrote: On 25-May-01 Norbert Preining wrote: According to ac ChangeLog: o Rip format conversion out of the pwc driver (me) | It belongs in user space.. This

RE: [CHECKER] large stack variables (>=1K) in 2.4.4 and 2.4.4-ac8

> From: Andrew Morton [mailto:[EMAIL PROTECTED]] > > Andreas Dilger wrote: > > > > On a side note, does anyone know if the kernel does checking if the > > stack overflowed at any time? > > There's a little bit of code in show_task() which calculates > how close this task ever got to

RE: Kernel 2.4.x TODO

> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > > Was the TODO list at http://linux24.sourceforge.net just > meant to be useful before 2.4.0 was released? I believe that is the case. > It seems to me that it would still be useful for (amongst > other things) > potential kernel hackers

RE: Kernel 2.4.x TODO

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Was the TODO list at http://linux24.sourceforge.net just meant to be useful before 2.4.0 was released? I believe that is the case. It seems to me that it would still be useful for (amongst other things) potential kernel hackers

RE: [CHECKER] large stack variables (=1K) in 2.4.4 and 2.4.4-ac8

From: Andrew Morton [mailto:[EMAIL PROTECTED]] Andreas Dilger wrote: On a side note, does anyone know if the kernel does checking if the stack overflowed at any time? There's a little bit of code in show_task() which calculates how close this task ever got to overrunning its kernel

RE: kernel2.2.x to kernel2.4.x

see http://www.firstfloor.org/~andi/softnet/ ~Randy > -Original Message- > From: jalaja devi [mailto:[EMAIL PROTECTED]] > > How can I handle this from kernel2.2 to kernel2.4 > > Can I replace like this?? > > if (test_and_set_bit (0, (void *)>tbusy)){ return > EBUSY;} == with

RE: kernel2.2.x to kernel2.4.x

see http://www.firstfloor.org/~andi/softnet/ ~Randy -Original Message- From: jalaja devi [mailto:[EMAIL PROTECTED]] How can I handle this from kernel2.2 to kernel2.4 Can I replace like this?? if (test_and_set_bit (0, (void *)dev-tbusy)){ return EBUSY;} == with

RE: LANANA: To Pending Device Number Registrants

hpa wrote: > > Alan Cox wrote: > > > > > Are FireWire (and USB) disks always detected in the same > > > order? Or does it > > > behave like ADB, where you never know which > > > mouse/keyboard is which mouse/keyboard? > > > > USB disks are required (haha etc) to have serial numbers. > >

RE: LANANA: To Pending Device Number Registrants

hpa wrote: Alan Cox wrote: Are FireWire (and USB) disks always detected in the same order? Or does it behave like ADB, where you never know which mouse/keyboard is which mouse/keyboard? USB disks are required (haha etc) to have serial numbers. Firewire similarly has

RE: kernel2.2.x to kernel2.4.x

> From: jalaja devi [mailto:[EMAIL PROTECTED]] > > I tried porting a network driver from kernel2.2.x to > 2.4. When i tried loading the driver, it shows the > unresolved symbols for > copy_to_user_ret > outs > __bad_udelay > > Could anyone please tell me the corresponding fxns in 2.4. You need

RE: kernel2.2.x to kernel2.4.x

From: jalaja devi [mailto:[EMAIL PROTECTED]] I tried porting a network driver from kernel2.2.x to 2.4. When i tried loading the driver, it shows the unresolved symbols for copy_to_user_ret outs __bad_udelay Could anyone please tell me the corresponding fxns in 2.4. You need to unroll

RE: [PATCH] x86 page fault handler not interrupt safe

> From: David Woodhouse [mailto:[EMAIL PROTECTED]] > > [EMAIL PROTECTED] said: > > If anybody has such a beast, please try this kernel patch _and_ > > running the F0 0F bug-producing program (search for it on the 'net - > > it must be out there somewhere) to verify that the code still > >

RE: [PATCH] x86 page fault handler not interrupt safe

From: David Woodhouse [mailto:[EMAIL PROTECTED]] [EMAIL PROTECTED] said: If anybody has such a beast, please try this kernel patch _and_ running the F0 0F bug-producing program (search for it on the 'net - it must be out there somewhere) to verify that the code still correctly

RE: inserting a Forth-like language into the Linux kernel

> > > If someone knows of another example of interpreter-like behavior > > > directly in a unix in-kernel thread I'd like to know about it. > > > > kdb > > > > That runs in trap handlers doesn't it? I don't think it's a > kernel daemon. and there's the hangman-in-kernel patch...

RE: inserting a Forth-like language into the Linux kernel

If someone knows of another example of interpreter-like behavior directly in a unix in-kernel thread I'd like to know about it. kdb That runs in trap handlers doesn't it? I don't think it's a kernel daemon. and there's the hangman-in-kernel patch... interpreter or daemon

RE: input core pointers, someone?

http://www.suse.cz/development/input/ and Vojtech Pavlik ([EMAIL PROTECTED]) ~Randy503-677-5408_ --- > -Original Message- > From: Magnus Bodin [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, May 02, 2001 7:18 AM >

RE: input core pointers, someone?

http://www.suse.cz/development/input/ and Vojtech Pavlik ([EMAIL PROTECTED]) ~Randy503-677-5408_ --- -Original Message- From: Magnus Bodin [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 02, 2001 7:18 AM To:

RE: Dyanmics Thread at Kernel Level

> On 26-Apr-2001 Rajeev Nigam wrote: > > Can anybody tell me, How can I create dynamic threads at > Kernel level?? > > > > If u have any sample code in which Semaphore, threads, events are > > implemented, Pls send. > > > > Waiting for ur response. > >

RE: Dyanmics Thread at Kernel Level

On 26-Apr-2001 Rajeev Nigam wrote: Can anybody tell me, How can I create dynamic threads at Kernel level?? If u have any sample code in which Semaphore, threads, events are implemented, Pls send. Waiting for ur response. http://www.linux-mag.com/depts/gear.html or

RE: [kbuild-devel] CML2 1.0.0 release announcement

www.tuxedo.org/~esr/cml2/transition.html>. > From: Eric S. Raymond [mailto:[EMAIL PROTECTED]] > > Dunlap, Randy <[EMAIL PROTECTED]>: > > I'd like to see one of the prominent web pages inform > > people that Python version x.yy(?) is required to use CML2. > > It's in the

RE: [kbuild-devel] CML2 1.0.0 release announcement

Hi Eric, > After 11 months of painstaking work and testing, CML2 1.0.0 > is ready for use, > and ready to replace the current kernel-configuration system. You'll > find it at . I've made a transition > guide available at

RE: [kbuild-devel] CML2 1.0.0 release announcement

Hi Eric, After 11 months of painstaking work and testing, CML2 1.0.0 is ready for use, and ready to replace the current kernel-configuration system. You'll find it at http://www.tuxedo.org/~esr/cml2/. I've made a transition guide available at

RE: [kbuild-devel] CML2 1.0.0 release announcement

. From: Eric S. Raymond [mailto:[EMAIL PROTECTED]] Dunlap, Randy [EMAIL PROTECTED]: I'd like to see one of the prominent web pages inform people that Python version x.yy(?) is required to use CML2. It's in the README. Is that good enough? -- Then the README should be listed (linked) on one

using ioctls (was: RE: Larger dev_t)

Hi- Tangential question (I think). Not for an IOCTL request 8;) [as the JFS request last week]. [When] is it OK to use (new) IOCTLs vs. using procfs read/write? And are there some alternative methods besides these two? Thanks, ~Randy > -Original Message- > From: Linus Torvalds

using ioctls (was: RE: Larger dev_t)

Hi- Tangential question (I think). Not for an IOCTL request 8;) [as the JFS request last week]. [When] is it OK to use (new) IOCTLs vs. using procfs read/write? And are there some alternative methods besides these two? Thanks, ~Randy -Original Message- From: Linus Torvalds

RE: HP Vectra XU 5/90 interrupt problems

> -Original Message- > From: John William [mailto:[EMAIL PROTECTED]] > > I'm having a problem with kernel 2.4.2-SMP on my HP Vectra XU > 5/90. This is an old dual-pentium (Neptune chipset) machine. > ... > > OR > > If PCI interrupts are shared, force them to be level > triggered?

RE: [patch] patch-2.4.2-irda1 (irda-usb)

> From: Jean Tourrilhes [mailto:[EMAIL PROTECTED]] > > First thanks for Dag for bringing me into the conversation. I > may add my little bit of spice, especially that I was the one pushing > for having the driver in .../drivers/net/irda. > By the way, Greg, sorry if I hurt your

RE: [patch] patch-2.4.2-irda1 (irda-usb)

From: Jean Tourrilhes [mailto:[EMAIL PROTECTED]] First thanks for Dag for bringing me into the conversation. I may add my little bit of spice, especially that I was the one pushing for having the driver in .../drivers/net/irda. By the way, Greg, sorry if I hurt your feeling, I

RE: USB mouse jumping

> From: Elmer Joandi [mailto:[EMAIL PROTECTED]] > > On Tue, 13 Feb 2001, Dunlap, Randy wrote: > > > If USB mice had serial numbers (like some USB storage devices > > do), then we could tell that it's the same mouse on the > > same connector and not change from m

RE: USB mouse jumping

> From: Elmer Joandi [mailto:[EMAIL PROTECTED]] > > I dont know, if it is bug or feature, but, > > USB mouse jumps around (between) /dev/input/mouse0 and mouse1 > when taken out and put back in(to same connector), 2.4.0 kernel. > > Annoys, should not be the default behaviour, IMHO. If USB

RE: USB mouse jumping

From: Elmer Joandi [mailto:[EMAIL PROTECTED]] I dont know, if it is bug or feature, but, USB mouse jumps around (between) /dev/input/mouse0 and mouse1 when taken out and put back in(to same connector), 2.4.0 kernel. Annoys, should not be the default behaviour, IMHO. If USB mice

RE: USB mouse jumping

From: Elmer Joandi [mailto:[EMAIL PROTECTED]] On Tue, 13 Feb 2001, Dunlap, Randy wrote: If USB mice had serial numbers (like some USB storage devices do), then we could tell that it's the same mouse on the same connector and not change from mouse0 to mouse1. Currently it looks like

RE: Unresolved Symbol error

> I am trying to create a catcher module that will provide a > distributed layer over the file system. To do this I am using > a kernel module to intercept and pre process the open system > call. However I need to use some functions such as strlen() > and memcpy() etc. When I try to compile

RE: Unresolved Symbol error

I am trying to create a catcher module that will provide a distributed layer over the file system. To do this I am using a kernel module to intercept and pre process the open system call. However I need to use some functions such as strlen() and memcpy() etc. When I try to compile the

RE: Mem detection problem

> From: Adam Schrotenboer [mailto:[EMAIL PROTECTED]] > > This is actually a repost of a problem that received few > serious replies (IMNSHO). Well, I claim not to have ignored it. I have gone thru the entire patch-2.4.1 file and can't see anything there that would cause what you are seeing.

RE: Mem detection problem

From: Adam Schrotenboer [mailto:[EMAIL PROTECTED]] This is actually a repost of a problem that received few serious replies (IMNSHO). Well, I claim not to have ignored it. I have gone thru the entire patch-2.4.1 file and can't see anything there that would cause what you are seeing. You

RE: different IRQ settings for different MPS settings?

Hi, > From: John R Lenton [mailto:[EMAIL PROTECTED]] > > With a MPS setting of 1.4 USB doesn't work on me; it timeouts, > constantly. With MPS setting of 1.1 everything is OK. > ... > > My question(s) is(are) is this a known bug, is this correct > behaviour, am I missing something, and why

RE: different IRQ settings for different MPS settings?

Hi, From: John R Lenton [mailto:[EMAIL PROTECTED]] With a MPS setting of 1.4 USB doesn't work on me; it timeouts, constantly. With MPS setting of 1.1 everything is OK. ... My question(s) is(are) is this a known bug, is this correct behaviour, am I missing something, and why is USB

kernel param. Q's

(Linux 2.4.0) 1. Are the PARIDE options that are listed in linux/Documentation/kernel-parameters.txt still valid? I couldn't find them in drivers/block/paride anywhere. 2. kernel-parameters.txt says (or implies to me) that ide?=nodma is a valid kernel option. However, I can't see this

Q. on marking __initdata

Hi, Just a question (not a patch proposal): Could +/* # of MP IRQ source entries */ +struct mpc_config_intsrc mp_irqs[MAX_IRQ_SOURCES]; in arch/i386/kernel/mpparse.c (in 2.4.1-ac3; or in arch/i386/kernel/io_apic.c in 2.4.1) be marked as __initdata ? If not, why not? Or is __initdata not

Q. on marking __initdata

Hi, Just a question (not a patch proposal): Could +/* # of MP IRQ source entries */ +struct mpc_config_intsrc mp_irqs[MAX_IRQ_SOURCES]; in arch/i386/kernel/mpparse.c (in 2.4.1-ac3; or in arch/i386/kernel/io_apic.c in 2.4.1) be marked as __initdata ? If not, why not? Or is __initdata not

RE: "kaweth" usb ethernet driver in 2.4?

It was posted on linux-usb-devel on 28-jan-2001. Find some email archive for it, or I can forward it to you... ~Randy > -Original Message- > From: Michael Rothwell [mailto:[EMAIL PROTECTED]] > Sent: Sunday, February 04, 2001 6:17 PM > To: Eric Sandeen > Cc: [EMAIL PROTECTED] > Subject:

RE: IDE timeouts 2.4.1

I'm also getting a ton of these, along with lots of file corruption. I could handle the timeouts and rebooting every once in awhile if I didn't also have the corruption. Do I have some incorrect IDE parameters? (using 2.4.0, not 2.4.1) dual Pentium III 933 MHz (STL2 board) SAMSUNG 20 GB IDE

RE: More on the VIA KT133 chipset misbehaving in Linux

> From: Rogerio Brito [mailto:[EMAIL PROTECTED]] > > While I don't have problems with the Duron above, I do have a > 486 here with 8MB of memory that I intend to use as a router > for my local LAN, but 2.4.0 only recognizes 7MB, while 2.2.18 > recognizes all 8MB. Under

RE: More on the VIA KT133 chipset misbehaving in Linux

From: Rogerio Brito [mailto:[EMAIL PROTECTED]] While I don't have problems with the Duron above, I do have a 486 here with 8MB of memory that I intend to use as a router for my local LAN, but 2.4.0 only recognizes 7MB, while 2.2.18 recognizes all 8MB. Under 2.4.0 (I

RE: IDE timeouts 2.4.1

I'm also getting a ton of these, along with lots of file corruption. I could handle the timeouts and rebooting every once in awhile if I didn't also have the corruption. Do I have some incorrect IDE parameters? (using 2.4.0, not 2.4.1) dual Pentium III 933 MHz (STL2 board) SAMSUNG 20 GB IDE

RE: [BUG] 2.4.1 Detects 64 MB RAM, actual 192MB

> From: Adam Schrotenboer [mailto:[EMAIL PROTECTED]] > > > On Wed, 31 Jan 2001 10:01:08 -0500, Adam Schrotenboer wrote: > > > >>> On Tue, 30 Jan 2001 23:25:22 -0500, Adam Schrotenboer wrote: > >>> > ... > Linux version 2.4.1 (root@tabriel) (gcc version egcs-2.91.66 > >>> > >>

RE: PCI IRQ routing problem in 2.4.0 (updated patch)

> From: Martin Diehl [mailto:[EMAIL PROTECTED]] ... > Linus' patch helps you, because it makes us trusting the > device's config > space over the routing table. Probably a good idea as long as BIOS'es > wouldn't start to set wrong values in config space too... ... > in fact vanilla 2.4.0 did

RE: PCI IRQ routing problem in 2.4.0 (updated patch)

From: Martin Diehl [mailto:[EMAIL PROTECTED]] ... Linus' patch helps you, because it makes us trusting the device's config space over the routing table. Probably a good idea as long as BIOS'es wouldn't start to set wrong values in config space too... ... in fact vanilla 2.4.0 did believe

RE: [BUG] 2.4.1 Detects 64 MB RAM, actual 192MB

From: Adam Schrotenboer [mailto:[EMAIL PROTECTED]] On Wed, 31 Jan 2001 10:01:08 -0500, Adam Schrotenboer wrote: On Tue, 30 Jan 2001 23:25:22 -0500, Adam Schrotenboer wrote: ... Linux version 2.4.1 (root@tabriel) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release))

RE: Multiplexing mouse input

The "USB Guide" section on HID devices could also be helpful to you. http://www.linux-usb.org/USB-guide/x194.html ~Randy / 503-677-5408 ___ > From: Ben Ford [mailto:[EMAIL PROTECTED]] > > You are probably talking about an Xfree issue. And yes it

RE: Multiplexing mouse input

The "USB Guide" section on HID devices could also be helpful to you. http://www.linux-usb.org/USB-guide/x194.html ~Randy / 503-677-5408 ___ From: Ben Ford [mailto:[EMAIL PROTECTED]] You are probably talking about an Xfree issue. And yes it

RE: [uPATCH][Probably fucked up] arch/i386/kernel/io_apic.c: missing extern? (241p10)

Rasmus, Yep, I noticed this during some recent ServerWorks chipset APIC work I have been doing. nr_ioapics is also used in arch/i386/kernel/apic.c (#ifdef CONFIG_X86_IO_APIC), so that should have an extern int nr_ioapics; also. I'd prefer to see nr_ioapics live near the mp_ioapics[] array,

RE: [uPATCH][Probably fucked up] arch/i386/kernel/io_apic.c: missing extern? (241p10)

Rasmus, Yep, I noticed this during some recent ServerWorks chipset APIC work I have been doing. nr_ioapics is also used in arch/i386/kernel/apic.c (#ifdef CONFIG_X86_IO_APIC), so that should have an extern int nr_ioapics; also. I'd prefer to see nr_ioapics live near the mp_ioapics[] array,

RE: Teledat USB 2 a/b

Some USB ISDN TAs work with Linux-USB. See http://www.qbik.ch/usb/devices/ + Device Overview + Comm. Several are listed there. The Teledat is not listed, so it may or may not work. You could try attaching the device with the "acm" driver loaded to see if the acm driver claims the device. ~Randy

RE: Teledat USB 2 a/b

Some USB ISDN TAs work with Linux-USB. See http://www.qbik.ch/usb/devices/ + Device Overview + Comm. Several are listed there. The Teledat is not listed, so it may or may not work. You could try attaching the device with the "acm" driver loaded to see if the acm driver claims the device. ~Randy

RE: 2.2.19pre6aa1 USB - Why do I get these?

> Previously unseen. What could be the cause of these messages? > (Abit BH6 (Intel BX), Logitech Mouseman+ USB) > > Jan 24 21:39:15 iq kernel: usb.c: bw_alloc reduced by 118 to 0 for 0 > requesters > Jan 24 21:39:16 iq kernel: usb.c: bw_alloc increased by 118 > to 118 for 1 requesters

RE: 2.2.19pre6aa1 USB - Why do I get these?

Previously unseen. What could be the cause of these messages? (Abit BH6 (Intel BX), Logitech Mouseman+ USB) Jan 24 21:39:15 iq kernel: usb.c: bw_alloc reduced by 118 to 0 for 0 requesters Jan 24 21:39:16 iq kernel: usb.c: bw_alloc increased by 118 to 118 for 1 requesters ..

RE: int. assignment on SMP + ServerWorks chipset

> From: Duncan Laurie [mailto:[EMAIL PROTECTED]] > > On Mon, 22 Jan 2001, Randy.Dunlap wrote: > > Hi Randy, > > Oops, I knew it was an STL2, but somehow couldn't get it right in the > message.. It looks like they both use ServerWorks LE chipsets, do you > know if the SBT2 has the same

RE: int. assignment on SMP + ServerWorks chipset

Hi Duncan, > From: Duncan Laurie [mailto:[EMAIL PROTECTED]] > > Hi Petr, > > I didn't consider that your hardware would have subtle differences > than Mr. Dunlap's Intel SBT2 board, but these could have made the > hard-coded values in the patch invalid. So instead try the attached > patch,

RE: int. assignment on SMP + ServerWorks chipset

Hi Duncan, From: Duncan Laurie [mailto:[EMAIL PROTECTED]] Hi Petr, I didn't consider that your hardware would have subtle differences than Mr. Dunlap's Intel SBT2 board, but these could have made the hard-coded values in the patch invalid. So instead try the attached patch, and this

RE: int. assignment on SMP + ServerWorks chipset

Hi Duncan, Your temporary patch enables my USB host controller and USB devices (mouse, hub, and keyboard) to work on an STL2 system. > From: Duncan Laurie [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, January 16, 2001 5:40 PM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; >

RE: int. assignment on SMP + ServerWorks chipset

Hi Duncan, Your temporary patch enables my USB host controller and USB devices (mouse, hub, and keyboard) to work on an STL2 system. From: Duncan Laurie [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 16, 2001 5:40 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED];

RE: [Patch] memparse should return long long

Why not (?): > diff -uNr 2.4.0-ac/lib/cmdline.c 2.4.0-ac-memparse/lib/cmdline.c > --- 2.4.0-ac/lib/cmdline.cMon Aug 28 11:42:45 2000 > +++ 2.4.0-ac-memparse/lib/cmdline.c Mon Jan 15 09:06:14 2001 > @@ -93,9 +93,9 @@ > * megabyte, or one gigabyte, respectively. > */ > > -unsigned

RE: [Patch] memparse should return long long

Why not (?): diff -uNr 2.4.0-ac/lib/cmdline.c 2.4.0-ac-memparse/lib/cmdline.c --- 2.4.0-ac/lib/cmdline.cMon Aug 28 11:42:45 2000 +++ 2.4.0-ac-memparse/lib/cmdline.c Mon Jan 15 09:06:14 2001 @@ -93,9 +93,9 @@ * megabyte, or one gigabyte, respectively. */ -unsigned long

RE: The latest instance in the A20 farce

> From: H. Peter Anvin [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 10, 2001 4:10 PM > > "Dunlap, Randy" wrote: > > > > a. The BIOS isn't required to have int. 0x15, AH=0x2401 [Appx. A], > >but that is handled by your patch. > >

RE: The latest instance in the A20 farce

hpa- I tested this patch on a Pentium dual-proc system (440GX) and on a Celeron system[1] (810) that lacks floppy, keyboard controller, maybe some other things. Linux 2.4.0 boots fine on each of these systems with this patch applied. I couldn't tell which method of enabling A20 was actually

RE: The latest instance in the A20 farce

hpa- I tested this patch on a Pentium dual-proc system (440GX) and on a Celeron system[1] (810) that lacks floppy, keyboard controller, maybe some other things. Linux 2.4.0 boots fine on each of these systems with this patch applied. I couldn't tell which method of enabling A20 was actually

RE: The latest instance in the A20 farce

From: H. Peter Anvin [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 10, 2001 4:10 PM "Dunlap, Randy" wrote: a. The BIOS isn't required to have int. 0x15, AH=0x2401 [Appx. A], but that is handled by your patch. Idiots. This should be required and be a nul

RE: USB problems with 2.4.0

What kind of USB host controller is it? Maybe there are some issues with it. Maybe 'lspci -vv'... ~Randy ___ |randy.dunlap_at_intel.com503-677-5408| --- > From: Adam Huffman [mailto:[EMAIL

RE: USB problems with 2.4.0

What kind of USB host controller is it? Maybe there are some issues with it. Maybe 'lspci -vv'... ~Randy ___ |randy.dunlap_at_intel.com503-677-5408| --- From: Adam Huffman [mailto:[EMAIL

RE: USB broken in 2.4.0

This rings a small bell with me. There was a change by Dan Streetman IIRC to limit usbdevfs bulk transfers to PAGE_SIZE (4 KB for x86, or 0x1000). Anything larger than that returns an error (-EINVAL). ~Randy ___ |randy.dunlap_at_intel.com

RE: Adding devices to dc2xx.c

> Hello, and thank you to those who responded to my query about > adding my > Agfa ePhoto to the USB mass storage device database. I had no success > with this (the machine locked hard on connecting the device), > so I have decided to try it with the dc2xx driver. > > I have added it to

RE: Adding devices to dc2xx.c

Hello, and thank you to those who responded to my query about adding my Agfa ePhoto to the USB mass storage device database. I had no success with this (the machine locked hard on connecting the device), so I have decided to try it with the dc2xx driver. I have added it to

RE: USB broken in 2.4.0

This rings a small bell with me. There was a change by Dan Streetman IIRC to limit usbdevfs bulk transfers to PAGE_SIZE (4 KB for x86, or 0x1000). Anything larger than that returns an error (-EINVAL). ~Randy ___ |randy.dunlap_at_intel.com

RE: usb dc2xx quirk

> From: David Brownell [mailto:[EMAIL PROTECTED]] > > If this makes it go away, then by all means apply this patch; > though I don't quite see what the failure mode would be. Josh didn't have HOTPLUG defined and he has confirmed to me that this patch fixes the oops. I'll forward it again. >

RE: usb dc2xx quirk

From: David Brownell [mailto:[EMAIL PROTECTED]] If this makes it go away, then by all means apply this patch; though I don't quite see what the failure mode would be. Josh didn't have HOTPLUG defined and he has confirmed to me that this patch fixes the oops. I'll forward it again. The

RE: recommended build environment

> From: Borislav Deianov [mailto:[EMAIL PROTECTED]] > > In article <[EMAIL PROTECTED]> you wrote: > >> > oWe tell vendors to build RPMv3 , glibc 2.1.x > >> Curious HOW do you tell vendors?? > > > When they ask. More usefully Dan Quinlann and most vendors > put together a > >

RE: recommended build environment

From: Borislav Deianov [mailto:[EMAIL PROTECTED]] In article [EMAIL PROTECTED] you wrote: oWe tell vendors to build RPMv3 , glibc 2.1.x Curious HOW do you tell vendors?? When they ask. More usefully Dan Quinlann and most vendors put together a recommended set of things to

RE: test12-pre6

> From: Linus Torvalds [mailto:[EMAIL PROTECTED]] > ... > Now, this is with a bog-standard PIIX irq router, so we > definitely know > that we have the pirq table parsing right. I even have unofficial > confirmation from intel engineers on this. > > But I see something obviously wrong there:

RE: test12-pre6

From: Linus Torvalds [mailto:[EMAIL PROTECTED]] ... Now, this is with a bog-standard PIIX irq router, so we definitely know that we have the pirq table parsing right. I even have unofficial confirmation from intel engineers on this. But I see something obviously wrong there: you have

RE: [bug] vfsmount->count accounting broken again?

> > Andries wrote Monday 4-dec-2000 about a umount patch > > for this: > > Randy, presumably you mean the userspace side, yes? I.e. not > the kernel > bug I reported. I should have put a subject [two bugs] > instead of [bug]. Right. Sorry I wasn't more clear about that. ~Randy - To

RE: [bug] vfsmount->count accounting broken again?

Andries wrote Monday 4-dec-2000 about a umount patch for this: Now that there was some discussion about umount, I released a version of mount/umount that perhaps has a slightly better behaviour. Since the change was largish (and is untested), don't put it blindly into your distribution. Another

RE: [bug] vfsmount-count accounting broken again?

Andries wrote Monday 4-dec-2000 about a umount patch for this: Now that there was some discussion about umount, I released a version of mount/umount that perhaps has a slightly better behaviour. Since the change was largish (and is untested), don't put it blindly into your distribution. Another

RE: [bug] vfsmount-count accounting broken again?

Andries wrote Monday 4-dec-2000 about a umount patch for this: Randy, presumably you mean the userspace side, yes? I.e. not the kernel bug I reported. I should have put a subject [two bugs] instead of [bug]. Right. Sorry I wasn't more clear about that. ~Randy - To unsubscribe from

RE: Nightly usb oops

Hi, What kernel (test10)? > -m /boot/System.map-2.4.0-test10 (specified) What compiler/version? Please post a list of your USB devices from /proc/bus/usb/devices . Are you inserting or unplugging a USB device when this happens? If not, are you doing anything with USB when this happens?

RE: Nightly usb oops

Hi, What kernel (test10)? -m /boot/System.map-2.4.0-test10 (specified) What compiler/version? Please post a list of your USB devices from /proc/bus/usb/devices . Are you inserting or unplugging a USB device when this happens? If not, are you doing anything with USB when this happens?

RE: usbdevfs mount 2x, umount 1x

> From: Jan-Benedict Glaw [mailto:[EMAIL PROTECTED]] > > On Wed, Nov 29, 2000 at 04:47:27PM -0800, Randy Dunlap wrote: > > > > Summary: After I mount usbdevfs 2 times, and umount it > > 1 time, the usbcore module use count prevents it from > > being rmmod-ed. > > > [root@dragon rdunlap]#

RE: usbdevfs mount 2x, umount 1x

From: Jan-Benedict Glaw [mailto:[EMAIL PROTECTED]] On Wed, Nov 29, 2000 at 04:47:27PM -0800, Randy Dunlap wrote: Summary: After I mount usbdevfs 2 times, and umount it 1 time, the usbcore module use count prevents it from being rmmod-ed. [root@dragon rdunlap]# lsmod usbcore

RE: usbdevfs mount 2x, umount 1x

> > > So umount it twice. > > I don't see a way to umount it twice or I would have done that. > > Is there a way? > > Erm... Say umount one more time? If _that_ doesn't work - we've got a > bug, either in umount(2) or in umount(8). Strace would be welcome. Or I'm using an old version of umount

RE: usbdevfs mount 2x, umount 1x

> From: Alexander Viro [mailto:[EMAIL PROTECTED]] > > On Wed, 29 Nov 2000, Randy Dunlap wrote: > > > [I reported this a couple of months back. Got no > > feedback on it. If it's just a DDT (don't do that) > > or a user error, please say so.] > > > > Summary: After I mount usbdevfs 2 times,

  1   2   3   >