Re: [linux-usb-devel] [PATCH] USB Config fix for 2.2.19-pre7

2001-01-11 Thread Franz Sirl
At 01:44 2001-01-11, Greg KH wrote: >Hi, > >Here's a fix for the USB Config for 2.2.19-pre7. I messed up and took >out the HID devices in the patch I sent you for 2.2.19-pre6. Why do the input handlers depend on CONFIG_USB_HID? On PPC we already have trouble with them depending on CONFIG_USB, s

Re: [linux-usb-devel] [PATCH] USB Config fix for 2.2.19-pre7

2001-01-12 Thread Franz Sirl
At 08:26 2001-01-12, Greg KH wrote: >On Thu, Jan 11, 2001 at 06:01:19PM +0100, Franz Sirl wrote: > > Why do the input handlers depend on CONFIG_USB_HID? On PPC we already have > > trouble with them depending on CONFIG_USB, so everybody has to select > > CONFIG_USB even if he

Re: asm-ppc/elf.h error

2000-11-27 Thread Franz Sirl
At 22:07 24.11.00, David Riley wrote: >In asm-ppc/elf.h, is not included. This breaks >compilations of anything that compiles it (e.g. binutils) because the >vector registers for Altivec aren't defined elsewhere. Included is a >quick diff. I didn't know which PPC maintainer to send this to, so

[PATCH] Missing PPC merge bits

2000-12-07 Thread Franz Sirl
Hi Linus, the appended patch contains the missing PPC bits for 2.4.0, patch OK'ed by Paul Mackerras. Franz. * drivers/char/keyboard.c: Use key_maps[0] instead of plain_map to enable proper keymap switching. * drivers/input/keybdev.c: Bring PPC keycode handling up-to-dat

[PATCH] t8p1: Fix input driver configuration

2000-08-29 Thread Franz Sirl
Resent as per Linus request. Franz. Hi, the attached patch does the following: * move input/Config.in in front of char/Config.in in all arch/*/config.in (already done in t7p7 for x86) * fix a small uncleanliness in char/keyboard.c, replace plain_map with key_maps[0] to enable correct run

Re: 2.2.18 signal.h

2000-12-15 Thread Franz Sirl
At 18:43 15.12.00, Andrea Arcangeli wrote: >On Fri, Dec 15, 2000 at 12:07:55PM -0500, Richard B. Johnson wrote: > > Current code makes perfect sense if you put a 'break;' after the last > >Current code makes perfect sense also without the break. I guess that's a >strict check to try to catch bugs,

Re: spin_lock forgets to clobber memory and other smp fixes [was Re: [patch] waitqueue optimization, 2.4.0-test7]

2000-09-07 Thread Franz Sirl
At 17:03 07.09.00, Andrea Arcangeli wrote: >On Mon, 4 Sep 2000, Andrea Arcangeli wrote: > > >barrier()). I also noticed __sti()/__save_flags() doesn't need to clobber > >"memory". > >I'm not sure anymore if __sti and spin_unlock() doesn't need to clobber >memory (it looks necessary to make sure th

Re: const __init

2001-05-20 Thread Franz Sirl
On Sunday 20 May 2001 21:51, Geert Uytterhoeven wrote: > Since a while include/linux/init.h contains the line > > * Also note, that this data cannot be "const". > > Why is this? Because const data will be put in a different section? Yes, and gcc3 errors on these constructs, cause it cannot d