Re: sparc64 section mismatch warnings

2008-02-20 Thread Sam Ravnborg
On Wed, Feb 20, 2008 at 10:28:39PM -0800, David Miller wrote: > From: Sam Ravnborg <[EMAIL PROTECTED]> > Date: Wed, 20 Feb 2008 22:50:20 +0100 > > > Full diff of the included changes below. > > > > If you can use this in part or in toal they have my: > > Signed-off-by: Sam Ravnborg <[EMAIL PROTEC

Re: sparc64 section mismatch warnings

2008-02-20 Thread David Miller
From: Sam Ravnborg <[EMAIL PROTECTED]> Date: Wed, 20 Feb 2008 22:50:20 +0100 > Full diff of the included changes below. > > If you can use this in part or in toal they have my: > Signed-off-by: Sam Ravnborg <[EMAIL PROTECTED]> Looks good, applied. Yes, this stuff is all only user past __init ti

Re: [PATCH v2][POWERPC] Fix initial lmb add region with a non-zero base

2008-02-20 Thread Josh Boyer
On Thu, 21 Feb 2008 13:15:58 +1100 Paul Mackerras <[EMAIL PROTECTED]> wrote: > Kumar Gala writes: > > > np. Are we trying to get this into 2.6.25 or .26? > > I was going to put it into my powerpc-next branch and put it in > 2.6.26. I don't see any need for it to go in 2.6.25. Is that a new br

Re: [PATCH v2][POWERPC] Fix initial lmb add region with a non-zero base

2008-02-20 Thread Paul Mackerras
David Miller writes: > I'm ambivalent but I would obviously prefer 2.6.25 because > it would allow me to proceed more easily with my sparc64 > NUMA work as well as get your bug fixes in more smoothly. Sounds like we should get Stephen to put it in linux-next-stable once we're convinced it's all O

Re: [PATCH v2][POWERPC] Fix initial lmb add region with a non-zero base

2008-02-20 Thread Paul Mackerras
Kumar Gala writes: > np. Are we trying to get this into 2.6.25 or .26? I was going to put it into my powerpc-next branch and put it in 2.6.26. I don't see any need for it to go in 2.6.25. Paul. - To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to

sparc64 section mismatch warnings

2008-02-20 Thread Sam Ravnborg
Hi David. I was looking into the few remaining section mismatch warnings on sparc64 (with my previous posted patchset applied). This is more an RFC than a real patch submission. Can you try to look through my mumblings and see if anything makes sense. The ones I have is: WARNING: vmlinux.o(.tex

Re: E10k porting efforts

2008-02-20 Thread Tonu Samuel
> The E10k that we have is currently powered off. We were not able to > finish our efforts to get a serial console driver before we lost our > hosting space. WTF?! I have three (!) e10k-s here from which one runs 24x7. Tell me what you need and I make it possible from hardware and access to it.

Re: E10k porting efforts

2008-02-20 Thread Tom "spot" Callaway
On Wed, 2008-02-20 at 15:02 +0100, Florian Fainelli wrote: > Hi all, > > Are there any public E10k porting efforts ? There is currently no > hardware driver for the serial console, and I read that people from > RedHat are working on it. > I could also arrange accounts on the SSP machine if peop

E10k porting efforts

2008-02-20 Thread Florian Fainelli
Hi all, Are there any public E10k porting efforts ? There is currently no hardware driver for the serial console, and I read that people from RedHat are working on it. I could also arrange accounts on the SSP machine if people are interested in working on this Sparc port. Thank you very much