On the size of compiled kernels (was: Re: acquiring an interrupt for swim3 floppy driver)

2005-04-14 Thread Rogério Brito
On Apr 13 2005, Brad Boyer wrote: > Also, ppc code is on average bigger than x86 code. It's just a property > of the instruction set. The x86 uses variable sized opcodes, so some > stuff is only one or two bytes. The ppc instruction set uses exactly 4 > bytes for everything. Yes, that I knew (I t

Re: acquiring an interrupt for swim3 floppy driver

2005-04-13 Thread Rogério Brito
On Apr 13 2005, Rogério Brito wrote: > I don't know if what I will say is orthogonal to the discussion that you're > having, but I noticed one thing: when using a 2.6 kernel (2.6.11 vanilla > here), I can't format a floppy with, say, superformat (from the fdutils > package). Just to leave things c

Re: acquiring an interrupt for swim3 floppy driver

2005-04-13 Thread Brad Boyer
On Wed, Apr 13, 2005 at 11:17:23PM -0300, Rog?rio Brito wrote: > P.S.: The 2.6 kernels, even though compiled with very few options (almost > the strict minimum for it to work) and "optimized for size", are quite > larger than an equivalently compiled 2.4 kernel... Perhaps GCC isn't that > good (as

Re: acquiring an interrupt for swim3 floppy driver

2005-04-13 Thread Rogério Brito
I don't know if what I will say is orthogonal to the discussion that you're having, but I noticed one thing: when using a 2.6 kernel (2.6.11 vanilla here), I can't format a floppy with, say, superformat (from the fdutils package). After I try to use superformat with /dev/fd0, I get messages tellin

Re: acquiring an interrupt for swim3 floppy driver

2005-04-13 Thread Benjamin Herrenschmidt
> No - my attempts right now were to get the driver to compile (by getting > rid of the old sti/cli/save_flags/restore_flags). I was able to do this > by getting rid of these functions and replacing them with the local_irq_ > equivalents, and the driver compiled, and even worked ;-) > > However,

Re: acquiring an interrupt for swim3 floppy driver

2005-04-13 Thread vinai
On Wed, 13 Apr 2005, Brad Boyer wrote: On Tue, Apr 12, 2005 at 07:37:16PM -0500, vinai wrote: I was wondering what was the best/cleanest (and SMP-safe) way to grab an interrupt ? swim3 currently uses local_irq_enable, but from past discussions on the list, it did not sound like it was SMP safe. A

Re: acquiring an interrupt for swim3 floppy driver

2005-04-13 Thread Brad Boyer
On Tue, Apr 12, 2005 at 07:37:16PM -0500, vinai wrote: > I was wondering what was the best/cleanest (and SMP-safe) way to grab > an interrupt ? swim3 currently uses local_irq_enable, but from past > discussions on the list, it did not sound like it was SMP safe. All > of the other local_irq_ code

acquiring an interrupt for swim3 floppy driver

2005-04-12 Thread vinai
Hi Folks, I was wondering what was the best/cleanest (and SMP-safe) way to grab an interrupt ? swim3 currently uses local_irq_enable, but from past discussions on the list, it did not sound like it was SMP safe. All of the other local_irq_ code seems to be easily enough bracketed off by equivale