On Fri, 2008-05-02 at 16:38 -0700, David Miller wrote:
> Oh, I forgot about how far function calls are done on powerpc.
> Yes, that will suck.
>
> Is there some way to map all of the modules in the low 32-bits and
> thus aovid the trampolines? The powerpc call instruction can cover
> 4GB like on
From: Benjamin Herrenschmidt <[EMAIL PROTECTED]>
Date: Sat, 03 May 2008 17:50:17 +1000
> Best would be if we could get those runtime bits linked in the module
> itself, but I don't know enough about our toolchain to know if that's
> easy (I suppose everything is always possible :-)
The only downs
On Sat, 2008-05-03 at 00:55 -0700, David Miller wrote:
> From: Benjamin Herrenschmidt <[EMAIL PROTECTED]>
> Date: Sat, 03 May 2008 17:50:17 +1000
>
> > Best would be if we could get those runtime bits linked in the module
> > itself, but I don't know enough about our toolchain to know if that's
>
>
> On Thu, 2008-05-01 at 15:13 +1000, Tony Breeds wrote:
> > On Tue, Apr 29, 2008 at 11:12:41PM -0700, David Miller wrote:
> > >
> > > This commit causes bootup failures on sparc64:
> > >
> > > commit 86f6dae1377523689bd8468fed2f2dd180fc0560
> > > Author: Yasunori Goto <[EMAIL PROTECTED]>
> > >
Now that of_i2c may be compiled as module, the header must be
exported for module compilation, as well.
Signed-off-by: Jochen Friedrich <[EMAIL PROTECTED]>
---
include/linux/of_i2c.h |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/include/linux/of_i2c.h b/include/linux/o
Hi all!
The same problem! I've tried 2.4.xx and 2.6.xx kernels. Nothing changed!
BUT. After many days of fucking with fs_enet driver I've found a
stable (as I see) solution. The bugs I've had:
- kernel oopses
- SKB data corruption
- BDs status corruption
- SKB ring full message
- too many RX
