> -Original Message-
> From: Stephen Rothwell [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, July 04, 2007 12:15 PM
> To: Li Yang-r58472
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED];
linuxppc-dev@ozlabs.org
> Subject: Re: [PATCH 2.6.23] 83xx USB platform code rework
>
> Hi Li,
>
> On Tue, 3
On Wed, 4 Jul 2007, Segher Boessenkool wrote:
> Your device is an rs5c372b. So, that's what you put in
> your device tree. Simple so far, right?
Yep.
> Now some OF I2C code goes looking for IIC devices in the
> device tree. It finds this thing, and from a table or
> something it derives that
Josh Boyer writes:
> Selfishly, that's why I listed it as June 2008 to begin with. We've got
> base 440 support in arch/powerpc now, but it needs more work. And I
> just started 405 this morning.
>
> However, I definitely want some date present when arch/ppc will go away.
> Otherwise it will la
On Wed, Jul 04, 2007 at 02:27:48PM +1000, Michael Ellerman wrote:
> Is this what other archs do?
They either use jiffies, or AFAICT an external counter that is
initialised to 0 at system powerup.
Yours Tony
linux.conf.auhttp://linux.conf.au/ || http://lca2008.linux.org.au/
Jan 28 -
On Wed, 2007-07-04 at 14:04 +1000, Tony Breeds wrote:
> When booting a current kernel with CONFIG_PRINTK_TIME enabled you'll
> see messages like:
>
> [0.00] time_init: decrementer frequency = 188.044000 MHz
> [0.00] time_init: processor frequency = 1504.352000 MHz
> [3712914.4362
Hi Li,
On Tue, 3 Jul 2007 17:43:16 +0800 Li Yang <[EMAIL PROTECTED]> wrote:
>
> Add 831x USB platform setup code and rework 834x USB
> platform setup code. Move USB platform code to usb.c
> for different boards with CPU of the same series to share
> the USB initialization code.
If there really
Signed-off-by: Tony Breeds <[EMAIL PROTECTED]>
---
This didn't get musch feedback the first time I posted it, so it's either
perfect ;P or it got missed.
arch/powerpc/kernel/vmlinux.lds.S |6 ++
include/asm-powerpc/cache.h |2 ++
2 files changed, 8 insertions(+)
Index: working/
Signed-off-by: Tony Breeds <[EMAIL PROTECTED]>
---
arch/powerpc/boot/Makefile | 10 ++
1 file changed, 10 insertions(+)
Index: working/arch/powerpc/boot/Makefile
===
--- working.orig/arch/powerpc/boot/Makefile
+++ working/a
When booting a current kernel with CONFIG_PRINTK_TIME enabled you'll
see messages like:
[0.00] time_init: decrementer frequency = 188.044000 MHz
[0.00] time_init: processor frequency = 1504.352000 MHz
[3712914.436297] Console: colour dummy device 80x25
This cause by the initiali
This is set of 3 patches that have been sent through the list as RFCs. I
believe that I've addressed any feedback that was raised. Each of the patches
is independant of the other and order is not important.
More feedback is always welcome.
Yours Tony
linux.conf.auhttp://linux.conf.au
Scott Wood writes:
> Is there any particular reason that of_device_is_compatible uses
> strncasecmp()? Besides the OF spec saying that names (and thus
> compatibles) are case sensitive, the "n" part screws up matching when a
> subset of a string is not a more generic version thereof. For exam
Paul-san,
Could you add these two patches?
[PATCH] of_serial: ignore unknown serial port
http://patchwork.ozlabs.org/linuxppc/patch?id=11421
[PATCH] of_serial: add port type checking
http://patchwork.ozlabs.org/linuxppc/patch?id=11422
Best regards,
Kou Ishizaki
___
Subject: PS3: Bootwrapper support.
Add support to build the PS3 flash rom image and remove some unneeded
lmb calls.
The PS3's lv1 loader supports loading gzipped binary images from flash
rom to addr zero. The loader enters the image at addr 0x100.
In this implementation a bootwrapper overlay is
>> Just use "compatible" exactly the way it is meant to be
>> used and your life will be so much simpler. And don't
>> even think about using a very generic property like "model"
>> for a purpose totally different from its intended purpose.
>
> AFAIU, the only way currently to attach an i2c device
>> What's the value add in doing this? The code to handle both cases
>> still
>> has to be in there (just under ifdef now). Is there actually any harm
>> in doing case-insensitive matching today, where things break because
>> there are conflicting properties with different cases?
>
> Not for case
>> How about a CONFIG_NOT_BROKEN_DEVICE_TREE that disables this and
>> other
>> legacy stuff? If unset, warnings will be printed whenever broken
>> things
>> are detected. Boards which need proper device tree parsing can
>> select
>> the config option.
>>
>> I'd prefer the other way around
On Tue, 3 Jul 2007, Segher Boessenkool wrote:
> Just use "compatible" exactly the way it is meant to be
> used and your life will be so much simpler. And don't
> even think about using a very generic property like "model"
> for a purpose totally different from its intended purpose.
AFAIU, the on
Olof Johansson wrote:
> On Tue, Jul 03, 2007 at 05:15:11PM -0500, Scott Wood wrote:
>
>
>>How about a CONFIG_NOT_BROKEN_DEVICE_TREE that disables this and other
>>legacy stuff? If unset, warnings will be printed whenever broken things
>>are detected. Boards which need proper device tree parsi
On Tue, Jul 03, 2007 at 05:15:11PM -0500, Scott Wood wrote:
> How about a CONFIG_NOT_BROKEN_DEVICE_TREE that disables this and other
> legacy stuff? If unset, warnings will be printed whenever broken things
> are detected. Boards which need proper device tree parsing can select
> the config o
Segher Boessenkool wrote:
> Huh? Are you saying things are matching on substrings?
> That's even more wrong!
Yes, unfortunately. I tried getting the BRG frequency from the fsl,cpm
node and I got the fsl,cpm-enet node instead. :-P
ucc_geth requires device_type == network to avoid matching ucc_g
> Is there any particular reason that of_device_is_compatible uses
> strncasecmp()?
It always has, so some things might break with certain
device trees when we make the matching more strict/correct.
> Besides the OF spec saying that names (and thus
> compatibles) are case sensitive, the "n" part
Is there any particular reason that of_device_is_compatible uses
strncasecmp()? Besides the OF spec saying that names (and thus
compatibles) are case sensitive, the "n" part screws up matching when a
subset of a string is not a more generic version thereof. For example,
ucc_geth v. ucc_geth_p
On Thu, Jun 28, 2007 at 10:55:04PM +1000, Paul Mackerras wrote:
> I have just pushed some more patches to the for-2.6.23 branch of
> powerpc.git. There are still more to go, of course. :)
>
> If anyone has a patch that was posted more than a couple of weeks ago
> that they want to go in and that
On Tue, Jun 26, 2007 at 10:18:11AM -0700, Mark A. Greer wrote:
> Actually, I wouldn't have a problem with getting rid of arch/ppc right
> now. It won't really be lost, just git checkout your favorite tag that
> still has it. It'll get rid of code people shouldn't be worrying about
> anymore anywa
On 7/3/07, Josh Boyer <[EMAIL PROTECTED]> wrote:
> > Please don't; us 4xx folks aren't yet ready. Active support for
> > Xilinx Virtex in arch/ppc only right now. I want to move over to
> > arch/powerpc; but end of year is rather aggressive.
>
> Selfishly, that's why I listed it as June 2008 to b
On Tue, 2007-07-03 at 11:03 -0600, Grant Likely wrote:
> On 7/3/07, Tom Gall <[EMAIL PROTECTED]> wrote:
> > June 2008 is a long time away to let this linger. Why not say by End of the
> > year 2007? That should give folks essentially two more 2.6 releases.
>
> Please don't; us 4xx folks aren't ye
On 7/3/07, Tom Gall <[EMAIL PROTECTED]> wrote:
> June 2008 is a long time away to let this linger. Why not say by End of the
> year 2007? That should give folks essentially two more 2.6 releases.
Please don't; us 4xx folks aren't yet ready. Active support for
Xilinx Virtex in arch/ppc only right
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED]
CC: linuxppc-dev@ozlabs.org
--
arch/powerpc/kernel/vmlinux.lds.S |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
Index: linux-2.6-lttng/arch/powerpc/kernel/vmlinux.lds.S
On Tue, 3 Jul 2007, Josh Boyer wrote:
> And Segher had made a suggestion that it could be officially killed
> during the PowerPC BOF at OLS 2008 for fun. But honestly, it doesn't
^^^
Or perhaps TLS/MLS/VLS/... (forgot about the 4th alternative location)? ;-)
With kind
Em Ter, 2007-07-03 às 04:01 -0500, Kumar Gala escreveu:
> Andrew,
>
> I was hoping to get your input on how to handle patches that cross
> maintainers. I've got a patch that is pretty PPC specific, but
> happens to touch some drivers as well.
>
> Here's the diffstat to get a rough idea:
>
>
On Tue, 2007-07-03 at 09:47 -0500, Tom Gall wrote:
> June 2008 is a long time away to let this linger. Why not say by End
> of the year 2007? That should give folks essentially two more 2.6
> releases.
A year seemed like the appropriate amount of time for an arch removal.
And Segher had made a su
June 2008 is a long time away to let this linger. Why not say by End of the
year 2007? That should give folks essentially two more 2.6 releases.
Regards,
Tom
On 7/3/07, Josh Boyer <[EMAIL PROTECTED]> wrote:
The arch/ppc tree has been in a semi-nebulous "bug fix only" state for a
few kernel r
On Tue, Jul 03, 2007 at 03:36:09PM +1000, Paul Mackerras wrote:
> The following patches have been added to the for-2.6.23 branch on
> powerpc.git. In addition, the master branch has the merge of the
> for-2.6.23 and merge branches, which means that it is up-to-date with
> Linus' 2.6.22-rc7 plus th
On Tue, Jul 03, 2007 at 04:01:20AM -0500, Kumar Gala wrote:
> Andrew,
>
> I was hoping to get your input on how to handle patches that cross
> maintainers. I've got a patch that is pretty PPC specific, but
> happens to touch some drivers as well.
I think the real question is why the heck doe
On Tue, Jul 03, 2007 at 03:36:09PM +1000, Paul Mackerras wrote:
> [POWERPC] spufs: Add stat file to spufs
> [POWERPC] spufs: Add spu stats in sysfs
These two should not go to Linus yet, they'll probably need quite a bit
of rework.
___
Linux
The arch/ppc tree has been in a semi-nebulous "bug fix only" state for a
few kernel releases now. The patch below officially declares this as of
the 2.6.22 kernel release and schedules arch/ppc for removal in June of
2008.
Signed-off-by: Josh Boyer <[EMAIL PROTECTED]>
---
Documentation/feature-
On Tue, 2007-07-03 at 15:36 +1000, Paul Mackerras wrote:
> The following patches have been added to the for-2.6.23 branch on
> powerpc.git. In addition, the master branch has the merge of the
> for-2.6.23 and merge branches, which means that it is up-to-date with
> Linus' 2.6.22-rc7 plus the patch
+ external-control;
Really?
>>>
>>> Well, is anybody actually using eciwx/ecowx?
>>
>> That's not the point -- the device tree should only
>> say "external-control" if the CPU actually supports
>> it; AFAIK, that's 601 only.
>
> I wonder whether you are mixing up ext
>>> + addr = of_get_property(node, "reg", &len);
>>> + if (!addr || len < sizeof(int) || *addr > 0x)
>>> + continue;
>>
>> Addresses aren't 16 bit AFAIK?
>
> Some i2c busses support 10 bits addressing...
All I2C busses. All I2C devices, too, it's just tha
> -Original Message-
> From: Joakim Tjernlund [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 03, 2007 7:20 PM
> To: Li Yang-r58472
> Cc: linuxppc-dev Development; Netdev; Fleming Andy-afleming
> Subject: RE: [PATCH] ucc_geth.c, make PHY device optional.
>
> On Tue, 2007-07-03 at 16:22 +08
On Tue, 2007-07-03 at 16:22 +0800, Li Yang-r58472 wrote:
> > -Original Message-
> > From: Joakim Tjernlund [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, July 03, 2007 3:21 PM
> > To: Li Yang-r58472
> > Cc: linuxppc-dev Development; Netdev; Fleming Andy-afleming
> > Subject: RE: [PATCH] ucc_g
On Tue, 2007-07-03 at 11:24 +0200, Marian Balakowicz wrote:
> Benjamin Herrenschmidt wrote:
> > On Thu, 2007-06-28 at 12:20 +0200, Marian Balakowicz wrote:
> >> I guess that with the above dropping of non-zero based PCI IO ranges
> >> this is not supposed to be working. But does anyone know why?
>
On Mon, Jul 02, 2007 at 01:51:42PM +0200, Segher Boessenkool wrote:
> >>+ external-control;
> >>
> >>Really?
> >
> >Well, is anybody actually using eciwx/ecowx?
>
> That's not the point -- the device tree should only
> say "external-control" if the CPU actually supports
> it; AFA
On Tue, 3 Jul 2007 04:01:20 -0500 Kumar Gala <[EMAIL PROTECTED]> wrote:
> Andrew,
>
> I was hoping to get your input on how to handle patches that cross
> maintainers. I've got a patch that is pretty PPC specific, but
> happens to touch some drivers as well.
>
> Here's the diffstat to get a
Add 831x USB platform setup code and rework 834x USB
platform setup code. Move USB platform code to usb.c
for different boards with CPU of the same series to share
the USB initialization code.
Signed-off-by: Li Yang <[EMAIL PROTECTED]>
Signed-off-by: Kim Phillips <[EMAIL PROTECTED]>
---
Respin fo
Benjamin Herrenschmidt wrote:
> On Thu, 2007-06-28 at 12:20 +0200, Marian Balakowicz wrote:
>> I guess that with the above dropping of non-zero based PCI IO ranges
>> this is not supposed to be working. But does anyone know why?
>
> We just fixed that for 64 bits but 32 bits still has the limitati
I'm still working through the back log of patches related to ppc32/
fsl. If there are patches people want to make sure get into 2.6.23
let me know.
David Gibson (2):
[POWERPC] Split out asm-ppc/mmu.h portions for Freescale Book-E
[POWERPC] Split out asm-ppc/mmu.h portions for Pow
Andrew,
I was hoping to get your input on how to handle patches that cross
maintainers. I've got a patch that is pretty PPC specific, but
happens to touch some drivers as well.
Here's the diffstat to get a rough idea:
arch/powerpc/kernel/io.c| 12 ++--
arch/powerpc/
On Tue, 2007-07-03 at 16:32, Kumar Gala wrote:
> On Jul 3, 2007, at 3:25 AM, Zang Roy-r61911 wrote:
>
> > Paul
> >
> > Could you help to add these patches:
> >
> > 1 add cuboot for 7448hpc2 board
> > http://ozlabs.org/pipermail/linuxppc-dev/2007-May/036834.html
>
> Reviewing this one.
>
It has b
On Jul 3, 2007, at 3:25 AM, Zang Roy-r61911 wrote:
> Paul
>
> Could you help to add these patches:
>
> 1 add cuboot for 7448hpc2 board
> http://ozlabs.org/pipermail/linuxppc-dev/2007-May/036834.html
Reviewing this one.
> 2. Remove redundant pci_read_irq_line() function for 85xx platform
> Acked
Paul
Could you help to add these patches:
1 add cuboot for 7448hpc2 board
http://ozlabs.org/pipermail/linuxppc-dev/2007-May/036834.html
2. Remove redundant pci_read_irq_line() function for 85xx platform
Acked by Ben
http://ozlabs.org/pipermail/linuxppc-dev/2007-June/037117.html
3. Fix e500 v2 c
> -Original Message-
> From: Joakim Tjernlund [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 03, 2007 3:21 PM
> To: Li Yang-r58472
> Cc: linuxppc-dev Development; Netdev; Fleming Andy-afleming
> Subject: RE: [PATCH] ucc_geth.c, make PHY device optional.
>
> On Tue, 2007-07-03 at 11:42 +08
On Tue, 2007-07-03 at 11:42 +0800, Li Yang-r58472 wrote:
> > -Original Message-
> > From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> > Behalf Of Joakim Tjernlund
> > Sent: Tuesday, July 03, 2007 8:52 AM
> > To: 'linuxppc-dev Development'; 'Netdev'; Li Yang-r58472
> > Subject: [PATCH
53 matches
Mail list logo
