On 9/28/09 5:41 PM, John Linn wrote:
>> -Original Message-
>> From: Richard Röjfors [mailto:richard.rojf...@mocean-labs.com]
>> Sent: Monday, September 28, 2009 8:22 AM
>> To: spi-devel-gene...@lists.sourceforge.net
>> Cc: linuxppc-...@ozlabs.org; dbrown...@users.sourceforge.net; Andrew Mor
>
> Thus spake Benjamin Herrenschmidt (b...@kernel.crashing.org):
>
> > On Thu, 2009-09-24 at 18:35 -0700, Rex Feany wrote:
> > >
> > > Then I can boot and get to a shell, but userspace is slow. 8 seconds
> > > to mount
> > > /proc (vs. less then a second using my old kernel)! Maybe this is an
> >
I think that you should start out with something of the sub-netbook type.
These are the next generation and coming up very soon. For a home computer
you need at least dual core and at those speeds it will need a very low
price and small footprint.
If you could sneak in on the sub-net quick perhaps
Speaking for myself, and I'm a small-time consultant to the local Small-Office
Home-Office market, I would wholeheartedly welcome the arrival to the market of
a PowerPC/Power motherboard. I would commission local builders to create
servers and desktops that would have that one extra layer of pr
one other idea (sorry)
Debian is not providing an altivec optimized version. If you want that you
have to go with Gentoo. If you were building cpu optimized from the ground
up with the libaltivec and perhaps the c++ altivec libraries (that require
translation for the changed library calls to all th
Thus spake Benjamin Herrenschmidt (b...@kernel.crashing.org):
> On Thu, 2009-09-24 at 18:35 -0700, Rex Feany wrote:
> >
> > Then I can boot and get to a shell, but userspace is slow. 8 seconds
> > to mount
> > /proc (vs. less then a second using my old kernel)! Maybe this is an
> > unrelated issu
> Here is the ld -M output for the "bad" compile:
>
> .data_nosave0xc0376790 0x870 load address 0x00376790
> 0xc0377000. = ALIGN (0x1000)
> *fill* 0xc0376790 0x870 00
Ah right. Having the ALIGN() inside the output section causes the linker
to
On Thu, 2009-09-24 at 15:21 +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next build (powerpc ppc44x_defconfig) failed like this:
>
> In file included from arch/powerpc/kvm/booke.c:31:
> arch/powerpc/kvm/timing.h: In function 'kvmppc_account_exit_stat':
> arch/powerpc/kvm/timing.h:51
Here is the ld -M output for the "bad" compile:
.data_nosave0xc0376790 0x870 load address 0x00376790
0xc0377000. = ALIGN (0x1000)
*fill* 0xc0376790 0x870 00
0xc0377000__nosave_begin = .
*(.data.nosave)
On 09/26/2009 05:38 AM, Konstantinos Margaritis wrote:
> I'm considering funding the design & production of a new PowerPC
> system (well, the motherboard, the rest are typical pc stuff and a
> case).
It might be interesting as a low-power system. For a development box,
this looks more intere
If you ignore the VMLINUX_SYMBOL, the only difference is moving the
ALIGN inside the brackets. If I move the ALIGN back where it was, then
the warning goes away.
But other sections moved the ALIGN without an issue. Could it be a
compiler problem? We are using version 4.0.0 (DENX ELDK 4.1 4.0.0).
On Fri, Aug 28, 2009 at 12:45:34AM -0500, Kumar Gala wrote:
>
> On Aug 18, 2009, at 5:04 PM, Anton Vorontsov wrote:
>
> >When cpm2.h included into spi_mpc8xxx driver, the SPI defines
> >in the header conflict with defines in the driver.
> >
> >We don't need them in the header file, so remove them
I looked into it some more the patch converts this section:
. = ALIGN(PAGE_SIZE);
.data_nosave : AT(ADDR(.data_nosave) - LOAD_OFFSET) {
__nosave_begin = .;
*(.data.nosave)
. = ALIGN(PAGE_SIZE);
__nosave_end = .;
> -Original Message-
> From: Richard Röjfors [mailto:richard.rojf...@mocean-labs.com]
> Sent: Monday, September 28, 2009 8:22 AM
> To: spi-devel-gene...@lists.sourceforge.net
> Cc: linuxppc-...@ozlabs.org; dbrown...@users.sourceforge.net; Andrew Morton;
> John Linn
> Subject: [PATCH v4] xi
This patch splits xilinx_spi into three parts, an OF and a platform
driver and generic part.
The generic part now also works on X86, it supports accessing the IP
booth big and little endian. There is also support for 16 and 32 bit
SPI for the Xilinx SPI IP DS570
Signed-off-by: Richard Röjfors
--
* Benjamin Herrenschmidt [2009-09-26 07:12:48]:
> On Fri, 2009-09-25 at 16:48 +0200, Peter Zijlstra wrote:
> > On Thu, 2009-09-24 at 10:51 +1000, Benjamin Herrenschmidt wrote:
> > > On Tue, 2009-09-15 at 14:11 +0200, Peter Zijlstra wrote:
> > > > I still think its a layering violation... its the
* Peter Zijlstra [2009-09-25 16:48:40]:
> On Thu, 2009-09-24 at 10:51 +1000, Benjamin Herrenschmidt wrote:
> > On Tue, 2009-09-15 at 14:11 +0200, Peter Zijlstra wrote:
> > > I still think its a layering violation... its the hypervisor manager
> > > that should be bothered in what state an off-lin
>
> Benjamin Herrenschmidt wrote on 28/09/2009
> 05:21:00:
> >
> > On Sun, 2009-09-27 at 15:22 +0200, Joakim Tjernlund wrote:
> > > > However, adding tlbil_va() to ptep_set_access_flags() as you suggested
> > > > makes everything happy. I need to test it some more, but it looks good
> > > > so fa
On Mon, 2009-09-28 at 18:07 +1000, Benjamin Herrenschmidt wrote:
> On Mon, 2009-09-28 at 17:45 +1000, Anton Blanchard wrote:
> > Hi,
> >
> > I've found at least one machine that wont boot 2.6.31-rc* with a
> > pseries_defconfig. If I move real-base from 0xc0 to 0xd0 it
> > boots fine.
> >
On Mon, 2009-09-28 at 17:45 +1000, Anton Blanchard wrote:
> Hi,
>
> I've found at least one machine that wont boot 2.6.31-rc* with a
> pseries_defconfig. If I move real-base from 0xc0 to 0xd0 it
> boots fine.
>
> # size vmlinux
>text data bss dec hex filename
> 9
Hi,
I've found at least one machine that wont boot 2.6.31-rc* with a
pseries_defconfig. If I move real-base from 0xc0 to 0xd0 it
boots fine.
# size vmlinux
textdata bss dec hex filename
9812942 1982496 1105228 12900666 c4d93a vmlinux
Looks like we blow right
Jean Delvare wrote on 28/09/2009 09:34:34:
>
> On Mon, 28 Sep 2009 09:30:32 +0200, Joakim Tjernlund wrote:
> > Jean Delvare wrote on 28/09/2009 09:28:09:
> > >
> > > On Mon, 28 Sep 2009 00:26:54 +0200, Joakim Tjernlund wrote:
> > > > Jean, I just noticed you pull request for i2c on LKML but I did
Benjamin Herrenschmidt wrote on 28/09/2009 09:34:46:
>
> On Mon, 2009-09-28 at 09:22 +0200, Joakim Tjernlund wrote:
> >
> > > happy to stick with it until somebody comes up with a real good
> > reason
> > > to do more :-) 8xx is on life support and has been around for long
> >
> > yeah, I figured
On Mon, 28 Sep 2009 00:26:54 +0200, Joakim Tjernlund wrote:
> Jean, I just noticed you pull request for i2c on LKML but I didn't see this
> patch nor have I got any feedback from you. What is your view?
My view is that i2c-mpc is nor under my jurisdiction, so I did not, and
will not, pay any atten
On Mon, 2009-09-28 at 09:22 +0200, Joakim Tjernlund wrote:
>
> > happy to stick with it until somebody comes up with a real good
> reason
> > to do more :-) 8xx is on life support and has been around for long
>
> yeah, I figured that too but Freescale seems to be cranking out new
> variants still
On Mon, 28 Sep 2009 09:30:32 +0200, Joakim Tjernlund wrote:
> Jean Delvare wrote on 28/09/2009 09:28:09:
> >
> > On Mon, 28 Sep 2009 00:26:54 +0200, Joakim Tjernlund wrote:
> > > Jean, I just noticed you pull request for i2c on LKML but I didn't see
> > > this
> > > patch nor have I got any feedb
> "Joakim" == Joakim Tjernlund writes:
Hi,
Joakim> Ah, that explains it. Who then will look after i2c-mpc? Kumar?
Ben Dooks (embedded i2c maintainer). He's afaik coming home today, so
give him a few days to catch up on mails.
--
Bye, Peter Korsgaard
__
Jean Delvare wrote on 28/09/2009 09:28:09:
>
> On Mon, 28 Sep 2009 00:26:54 +0200, Joakim Tjernlund wrote:
> > Jean, I just noticed you pull request for i2c on LKML but I didn't see this
> > patch nor have I got any feedback from you. What is your view?
>
> My view is that i2c-mpc is nor under my
Benjamin Herrenschmidt wrote on 28/09/2009 05:21:00:
>
> On Sun, 2009-09-27 at 15:22 +0200, Joakim Tjernlund wrote:
> > > However, adding tlbil_va() to ptep_set_access_flags() as you suggested
> > > makes everything happy. I need to test it some more, but it looks good
> > > so far. Below is what
29 matches
Mail list logo
