* How to pass information from the bootloader to the kernel ?
From: Laurent Pinchart @ 2008-04-10 15:50 UTC (permalink / raw)
To: linuxppc-dev
[-- Attachment #1: Type: text/plain, Size: 720 bytes --]
Hi everybody,
I need to pass a limited amount of information from the boot loader to the
Linux kernel, such as the boot mode chosen by the user or the last boot
reason (power up, reset, watchdog, ...).
What is the best way to pass that kind of information from the boot loader to
the kernel ? Should I use the device tree ?
I thought about populating the chosen node with the data I need. This could
make sense for the boot mode, but I feel like I would abuse the chosen node
if I used it to pass other "non user chosen" information.
Best regards,
--
Laurent Pinchart
CSE Semaphore Belgium
Chaussee de Bruxelles, 732A
B-1410 Waterloo
Belgium
T +32 (2) 387 42 59
F +32 (2) 387 42 75
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply
* Re: [PATCH v2] [POWER] mpc85xx_ds add DMA engine to the DT and parse it.
From: Sebastian Siewior @ 2008-04-10 15:39 UTC (permalink / raw)
To: Kumar Gala; +Cc: linuxppc-embedded
In-Reply-To: <049046C0-900B-449D-AA81-18A023E21C83@kernel.crashing.org>
* Kumar Gala | 2008-04-10 10:33:11 [-0500]:
>>>I also added updating the defconfig to enable the driver by default.
>>I just noticed that commit 049c9d455 renamed the ids. I couldn't find
>>this commit in your git tree. Did you rename the ids in the .dts file
>>(or want me to do this)?
>
>I think they are already in sync am I missing something?
Ah, the .dts has mpc8544* and eloplus* so it should be fine. Just got
confused by the another commit.
>- k
Sebastian
^ permalink raw reply
* Re: patches for 2.6.26
From: Kumar Gala @ 2008-04-10 15:36 UTC (permalink / raw)
To: Laurent Pinchart; +Cc: linuxppc-dev
In-Reply-To: <200804101720.36975.laurentp@cse-semaphore.com>
On Apr 10, 2008, at 10:20 AM, Laurent Pinchart wrote:
> On Thursday 10 April 2008 16:21, Kumar Gala wrote:
>> Guy's
>>
>> if you have work you want in 2.6.26 related to Freescale PPC's let me
>> know. Ideally you can provide links to the patches in
>> http://patchwork.ozlabs.org/linuxppc/
>
> Could you please add this one ?
>
> fs_enet: Don't call NAPI functions when NAPI is not used.
> http://patchwork.ozlabs.org/linuxppc/patch?id=17055
Jeff Garzik should ack this first. (you'll want to send to netdev and
Jeff).
(also ask him if he want it to go via netdev or ppc tree's).
- k
^ permalink raw reply
* Re: [PATCH v2] [POWER] mpc85xx_ds add DMA engine to the DT and parse it.
From: Kumar Gala @ 2008-04-10 15:33 UTC (permalink / raw)
To: Sebastian Siewior; +Cc: linuxppc-embedded
In-Reply-To: <20080410151206.GA21517@www.tglx.de>
On Apr 10, 2008, at 10:12 AM, Sebastian Siewior wrote:
> * Kumar Gala | 2008-04-10 09:46:39 [-0500]:
>
>>> This is a modified entry I found in the documentation for the 8544.
>>>
>>> Signed-off-by: Sebastian Siewior <bigeasy@linutronix.de>
>>> ---
>>> arch/powerpc/boot/dts/mpc8544ds.dts | 41 +++++++++++++++++++
>>> ++
>>> +++++++++
>>> arch/powerpc/platforms/85xx/mpc85xx_ds.c | 13 +++++++++
>>> 2 files changed, 54 insertions(+), 0 deletions(-)
>>
>> applied.
> Thank you.
>
>> I also added updating the defconfig to enable the driver by default.
> I just noticed that commit 049c9d455 renamed the ids. I couldn't find
> this commit in your git tree. Did you rename the ids in the .dts file
> (or want me to do this)?
I think they are already in sync am I missing something?
- k
^ permalink raw reply
* Re: [PATCH v2] E500 Make steal_context SMP-safe.
From: Kumar Gala @ 2008-04-10 15:31 UTC (permalink / raw)
To: Randy Vinson; +Cc: linuxppc-dev@ozlabs.org
In-Reply-To: <47F509CC.9010205@mvista.com>
On Apr 3, 2008, at 11:46 AM, Randy Vinson wrote:
> When steal_context is used on SMP systems, it can steal a context in
> use by one of the other processors. This patch adds context tracking
> to
> prevent this as suggested by BenH.
Can we be more descriptive in the problem/bug symptom in the
description.
otherwise this looks ok to me. I'd like BenH to ack as well since
he's been look at this code recently.
>
> Signed-off-by: Randy Vinson <rvinson@mvista.com>
> ---
> The previous version of this patch had some unnecessary code which
> has been
> removed in this version.
>
> Note: This is a proof-of-concept patch. This isn't my area of
> expertise,
> so I'd greatly appreciate any guidance I can get. I'm considering the
> use of for_each_online_cpu() instead of for_each_possible_cpu() and
> possibly putting the changes under a CONFIG_SMP switch to prevent
> unnecessary
> overhead in the non-SMP case.
for_each_online_cpu() is probably better. I'm guessing this optimizes
pretty well in the !CONFIG_SMP case.
- k
^ permalink raw reply
* Re: State of the MPC5200 PSC AC97 driver
From: Matt Sealey @ 2008-04-10 15:25 UTC (permalink / raw)
To: Marian Balakowicz; +Cc: linuxppc-dev, Sylvain Munaut, spitzauer_77
In-Reply-To: <47FDEF9B.5000506@semihalf.com>
I have a copy of the driver I hacked to work with the new PSC framework
but it doesn't "work" anymore - I have no idea why.
Mail me privately if you want it, I have no time to make patches or
look for a good reason for the breakages, but it compiles at least.
The Efika hack should be gone now (irrelevant since we released a firmware
that obseletes it) and the other fixmes should be by the wayside
considering the fscking thing doesn't play sound anymore...
--
Matt Sealey <matt@genesi-usa.com>
Genesi, Manager, Developer Relations
Marian Balakowicz wrote:
> Hi Sylvain,
>
> Last year you have posted a MPC5200 PSC AC97 driver patch
> "[PATCH 9/9] sound: Add support for Freescale MPC5200 AC97 interface."
> with the following comment:
>
>> Not quite a clean driver, but it get things done (well, mostly).
>> Only included to be able to test functionalityi/usage of
>> the BestComm driver.
>
> There are various FIXMEs and commented out code here and there.
> Could you elaborate a bit on the overall state of the driver's
> functionality,
> which areas need improvement and attention?
>
> Seems that you mainly tested BestComm with this driver, what was the
> overall
> BestComm performance, any issues here? Did you use any specific test setup
> involving some dedicated application, etc.?
>
> Did anyone else tried it and/or has a updated version or can share
> experience?
>
> Thanks in advance.
>
> Cheers,
> m.
^ permalink raw reply
* Re: patches for 2.6.26
From: Laurent Pinchart @ 2008-04-10 15:20 UTC (permalink / raw)
To: linuxppc-dev
In-Reply-To: <D9A4BB4A-970C-4E9E-9174-BA8C0191CCA2@kernel.crashing.org>
On Thursday 10 April 2008 16:21, Kumar Gala wrote:
> Guy's
>
> if you have work you want in 2.6.26 related to Freescale PPC's let me
> know. Ideally you can provide links to the patches in
> http://patchwork.ozlabs.org/linuxppc/
Could you please add this one ?
fs_enet: Don't call NAPI functions when NAPI is not used.
http://patchwork.ozlabs.org/linuxppc/patch?id=17055
--
Laurent Pinchart
CSE Semaphore Belgium
Chaussee de Bruxelles, 732A
B-1410 Waterloo
Belgium
T +32 (2) 387 42 59
F +32 (2) 387 42 75
^ permalink raw reply
* RE: Access physical memory via mmap() on ppc440epx.
From: Leonid @ 2008-04-10 15:15 UTC (permalink / raw)
To: Josh Boyer; +Cc: linuxppc-embedded
In-Reply-To: <406A31B117F2734987636D6CCC93EE3C033A9D08@ehost011-3.exch011.intermedia.net>
Hi, Josh:
I have double checked, mmap64 doesn't work either. This is the piece of
code which does re-mapping:
unsigned long long StartAddressL =3D 0x100000000ULL | StartAddress;
mmap_addr =3D (unsigned int) mmap64(NULL,=20
size,=20
PROT_READ | PROT_WRITE,
MAP_SHARED,=20
dev_mem_fd,=20
StartAddressL);
While in GDB I can see variables' values:
(gdb) p/x mmap_addr
$1 =3D 0x30028000
(gdb) p/x StartAddressL
No symbol "StartAddressL" in current context.
(gdb) p/x StartAddress
$2 =3D 0xfc240000
(gdb) p/x size
$3 =3D 0x60000
(gdb)
This call returns successfully, but when I stop the board and dump TLB
entries (I have BDI2000 connected) on BDI2000 screen, there is no entry
with this physical address.
However when I also do re-mapping (using ioremap64()) in kernel driver
(physical address is different - 0xea000000), this is the code:
if((mcfp_ebi_baseptr =3D ioremap64 (0x1ea000000ULL, 512)) =3D=3D NULL) {
...
When I stop in debugger right after remapping, TLB entry shows up but
somewhat non-completed yet:
10 : 00 00000000 1KB -0 -> 1_ea000000 U:0000 -I-G- XWRXWR
Later, when I stop board right BEFORE actual accessing memory, the entry
is
present:
23 : 00 d1050000 4KB V0 -> 1_ea000000 U:0000 -IMG- ----WR
And kernel driver is working.
So something is definitely wrong with mmap/mmap64 call itself. Should I
use different parameters?=20
Thanks,
Leonid.
-----Original Message-----
From: linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org
[mailto:linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org] On =
Behalf
Of Leonid
Sent: Wednesday, April 02, 2008 3:51 PM
To: Josh Boyer
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: Access physical memory via mmap() on ppc440epx.
Hi, Josh:
I have resolved my kernel driver problem, it was my own bug, didn't have
anything to do with memory remapping itself. Your suggestion to move to
ioremap64() did resolve problem completely.
I still need investigate mmap() crash. Apparently switch to mmap64()
didn't help, but it could be some another bug, I'll double check.
Thanks,
Leonid.=20
-----Original Message-----
From: linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org
[mailto:linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org] On =
Behalf
Of Leonid
Sent: Tuesday, April 01, 2008 9:30 PM
To: Josh Boyer
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: Access physical memory via mmap() on ppc440epx.
Hi, Josh:
Thank you for your suggestion. Somehow it didn't work with mmap (may be,
my mistake, I'll double check), however it partially helped me with my
another problem.
I have kernel driver where I need read/write some HW device, connected
on address 0xea000000, chip select 4. This chip select configured
properly, here are EBC registers:
440EPx>rd ebc0_b4cr
ebc0_b4cr: 0xea01a000 -368992256
440EPx>rd ebc0_b4ap
ebc0_b4ap: 0x03037000 50556928
>From u-boot I can read/write this address with no problem (I use md/mw
commands).
In my driver I tried to ioremap() this address and any attempt to access
led to crash, same as with mmap().
When, following your suggestion, I used address 0x1ea00000 and
ioremap64(), crashes disappeared!
I even can write, but when I read data back I see least significant byte
of each 16 bits word only (bus is configured 16 bits width).=20
What can it be?
Thanks,
Leonid.=20
-----Original Message-----
From: Josh Boyer [mailto:jwboyer@gmail.com]
Sent: Tuesday, April 01, 2008 6:44 PM
To: Leonid
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Access physical memory via mmap() on ppc440epx.
On Tue, 2008-04-01 at 14:12 -0700, Leonid wrote:
> Hi:
>=20
> I am trying to read from NOR flash, located on address 0xfc000000, on
my
It's at 0x1fc000000 IIRC.
> TLB entries look strange though. That what it was on u-boot stage:
>=20
> 440EPx>tlb 0 10
> IDX TID EPN SIZE VTS RPN USER WIMGE USRSVC
> 0 : 00 40000000 256MB V0 -> 0_00000000 U:0000 -I-G- XWRXWR
> 1 : 00 00000000 256MB V0 -> 0_00000000 U:0000 -I-G- XWRXWR
> 2 : 00 c0000000 256MB V0 -> 1_c0000000 U:0000 -I-G- XWRXWR
> 3 : 00 f0000000 256MB V0 -> 1_f0000000 U:0000 WI-G- XWRXWR
See. Virtual is 0xf0000000, physical is 0x1f0000000.
> On Linux stage it looks rather different:
I don't even see your entry in here. Likely because the TLB is small
and it's gone by the time you do the dump
> Probably under MMU it should look this way? How to use mmap() then?
Try mmap64 on the real physical address and see if that helps.
josh
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
^ permalink raw reply
* Re: [PATCHv4 0/5] cpm2: Reset the CPM at startup and fix the cpm_uart driver accordingly.
From: Kumar Gala @ 2008-04-10 15:14 UTC (permalink / raw)
To: Laurent Pinchart; +Cc: Scott Wood, linuxppc-dev
In-Reply-To: <200804011433.29841.laurentp@cse-semaphore.com>
On Apr 1, 2008, at 7:33 AM, Laurent Pinchart wrote:
> Hi everybody,
>
> these 5 patches reset the CPM in cpm2_reset() and fix the cpm_uart
> driver to
> initialise SMC ports correctly without relying on any initialisation
> performed by the boot loader/wrapper. They update the boot wrapper
> code and
> the EP8248E device tree to match the new SMC registers description.
>
> Patches 2/5, 3/5 and 4/5 (boot wrapper and EP8248E device tree
> updates)
> haven't been tested due to lack of hardware.
applied.
- k
^ permalink raw reply
* Re: [PATCH v2] [POWER] mpc85xx_ds add DMA engine to the DT and parse it.
From: Sebastian Siewior @ 2008-04-10 15:12 UTC (permalink / raw)
To: Kumar Gala; +Cc: linuxppc-embedded
In-Reply-To: <B4CD3ECE-5F98-4A7B-A811-A84EADA804CF@kernel.crashing.org>
* Kumar Gala | 2008-04-10 09:46:39 [-0500]:
>>This is a modified entry I found in the documentation for the 8544.
>>
>>Signed-off-by: Sebastian Siewior <bigeasy@linutronix.de>
>>---
>>arch/powerpc/boot/dts/mpc8544ds.dts | 41 +++++++++++++++++++++
>>+++++++++
>>arch/powerpc/platforms/85xx/mpc85xx_ds.c | 13 +++++++++
>>2 files changed, 54 insertions(+), 0 deletions(-)
>
>applied.
Thank you.
>I also added updating the defconfig to enable the driver by default.
I just noticed that commit 049c9d455 renamed the ids. I couldn't find
this commit in your git tree. Did you rename the ids in the .dts file
(or want me to do this)?
>- k
Sebastian
^ permalink raw reply
* ppc64 build issue
From: Kumar Gala @ 2008-04-10 15:01 UTC (permalink / raw)
To: ppc-dev list
anyone looking into this?
http://kisskb.ellerman.id.au/kisskb/buildresult/23299/
Its really a Kconfig issue.
- k
^ permalink raw reply
* Re: [PATCH v2] [POWER] mpc85xx_ds add DMA engine to the DT and parse it.
From: Kumar Gala @ 2008-04-10 14:46 UTC (permalink / raw)
To: Sebastian Siewior; +Cc: linuxppc-embedded
In-Reply-To: <20080314230130.GA6812@www.tglx.de>
On Mar 14, 2008, at 6:01 PM, Sebastian Siewior wrote:
> This is a modified entry I found in the documentation for the 8544.
>
> Signed-off-by: Sebastian Siewior <bigeasy@linutronix.de>
> ---
> arch/powerpc/boot/dts/mpc8544ds.dts | 41 +++++++++++++++++++++
> +++++++++
> arch/powerpc/platforms/85xx/mpc85xx_ds.c | 13 +++++++++
> 2 files changed, 54 insertions(+), 0 deletions(-)
applied.
I also added updating the defconfig to enable the driver by default.
- k
^ permalink raw reply
* Re: Patches added to powerpc.git powerpc-next and master branches
From: Kumar Gala @ 2008-04-10 14:44 UTC (permalink / raw)
To: Laurent Pinchart; +Cc: linuxppc-dev, paulus
In-Reply-To: <200804101346.32376.laurentp@cse-semaphore.com>
On Apr 10, 2008, at 6:46 AM, Laurent Pinchart wrote:
> Hi Paul,
>
> could you please add the following patches ?
>
> [PATCHv4 1/5] cpm_uart: Allocate DPRAM memory for SMC ports on CPM2-
> based
> platforms.
> http://ozlabs.org/pipermail/linuxppc-dev/2008-April/053858.html
>
> [PATCHv4 2/5] powerpc: Add bootwrapper function to get virtual reg
> from the
> device tree.
> http://ozlabs.org/pipermail/linuxppc-dev/2008-April/053859.html
>
> [PATCHv4 3/5] cpm-serial: Relocate CPM buffer descriptors and SMC
> parameter
> ram.
> http://ozlabs.org/pipermail/linuxppc-dev/2008-April/053860.html
>
> [PATCHv4 4/5] ep8248e: Reference SMC parameter RAM base in the
> device tree.
> http://ozlabs.org/pipermail/linuxppc-dev/2008-April/053862.html
>
> [PATCHv4 5/5] cpm2: Reset the CPM when early debugging is not enabled.
> http://ozlabs.org/pipermail/linuxppc-dev/2008-April/053861.html
Your patches still have mailer issues when I try to apply them.
If you want to go back and forth privately so we can figure out what's
going on.
- k
^ permalink raw reply
* Re: Patches added to powerpc.git powerpc-next and master branches
From: Kumar Gala @ 2008-04-10 14:33 UTC (permalink / raw)
To: Laurent Pinchart; +Cc: linuxppc-dev, Paul Mackerras
In-Reply-To: <200804101628.49877.laurentp@cse-semaphore.com>
On Apr 10, 2008, at 9:28 AM, Laurent Pinchart wrote:
> On Thursday 10 April 2008 16:11, Kumar Gala wrote:
>>
>> On Apr 10, 2008, at 7:32 AM, Paul Mackerras wrote:
>>> Laurent Pinchart writes:
>>>
>>>> could you please add the following patches ?
>>>
>>> Sure, if Kumar acks them, since they are all 8xxx-related as far
>>> as I
>>> can see (with the exception of the part of 2/5 that adds the new
>>> dt_get_virtual_reg function). Or Kumar can put them in his tree.
>>
>> I'll deal with them. There are a larger number of CPM/8xxx related
>> patches that I need to go through.
>
> Is there a chance they could go in 2.6.26 ?
Yes that's the idea :)
- k
^ permalink raw reply
* Re: [PATCH 1 of 3] [POWERPC 44x] Export tlb_44x_hwater for KVM
From: Josh Boyer @ 2008-04-10 14:30 UTC (permalink / raw)
To: Hollis Blanchard; +Cc: kvm-devel, linuxppc-dev, kvm-ppc-devel
In-Reply-To: <d1804f03574745f4f8f5.1207601612@localhost.localdomain>
On Mon, 07 Apr 2008 15:53:32 -0500
Hollis Blanchard <hollisb@us.ibm.com> wrote:
> 1 file changed, 2 insertions(+)
> include/asm-powerpc/mmu-44x.h | 2 ++
>
>
> PowerPC 440 KVM needs to know how many TLB entries are used for the host kernel
> linear mapping (it does not modify these mappings when switching between guest
> and host execution).
>
> Signed-off-by: Hollis Blanchard <hollisb@us.ibm.com>
Acked-by: Josh Boyer <jwboyer@linux.vnet.ibm.com>
>
> diff --git a/include/asm-powerpc/mmu-44x.h b/include/asm-powerpc/mmu-44x.h
> --- a/include/asm-powerpc/mmu-44x.h
> +++ b/include/asm-powerpc/mmu-44x.h
> @@ -53,6 +53,8 @@
>
> #ifndef __ASSEMBLY__
>
> +extern unsigned int tlb_44x_hwater;
> +
> typedef unsigned long long phys_addr_t;
>
> typedef struct {
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
^ permalink raw reply
* Re: Patches added to powerpc.git powerpc-next and master branches
From: Laurent Pinchart @ 2008-04-10 14:28 UTC (permalink / raw)
To: Kumar Gala; +Cc: linuxppc-dev, Paul Mackerras
In-Reply-To: <EA6AD0FF-DBB4-4835-A77B-EE337BAB53E2@kernel.crashing.org>
[-- Attachment #1: Type: text/plain, Size: 745 bytes --]
On Thursday 10 April 2008 16:11, Kumar Gala wrote:
>
> On Apr 10, 2008, at 7:32 AM, Paul Mackerras wrote:
> > Laurent Pinchart writes:
> >
> >> could you please add the following patches ?
> >
> > Sure, if Kumar acks them, since they are all 8xxx-related as far as I
> > can see (with the exception of the part of 2/5 that adds the new
> > dt_get_virtual_reg function). Or Kumar can put them in his tree.
>
> I'll deal with them. There are a larger number of CPM/8xxx related
> patches that I need to go through.
Is there a chance they could go in 2.6.26 ?
Best regards,
--
Laurent Pinchart
CSE Semaphore Belgium
Chaussee de Bruxelles, 732A
B-1410 Waterloo
Belgium
T +32 (2) 387 42 59
F +32 (2) 387 42 75
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply
* Re: [PATCH 0 of 3] KVM for PowerPC 440
From: Hollis Blanchard @ 2008-04-10 14:26 UTC (permalink / raw)
To: Josh Boyer; +Cc: kvm-devel, linuxppc-dev, kvm-ppc-devel
In-Reply-To: <20080410065518.46979767@zod.rchland.ibm.com>
On Thursday 10 April 2008 06:55:18 Josh Boyer wrote:
> On Mon, 07 Apr 2008 15:53:31 -0500
>
> Hollis Blanchard <hollisb@us.ibm.com> wrote:
> > Implement initial support for KVM for PowerPC 440. There are just two
> > small prerequisite patches, and then the bulk of the code can't be split
> > easily.
> >
> > Please review; I would like to submit these for 2.6.26. There is plenty
> > of work to do, both functional and optimization, but this code is
> > sufficient to run unmodified 440 Linux guests on a 440 Linux host. What's
> > your favorite bike shed color?
>
> Who's tree are you looking to get this patch set into?
Since the only PPC-specific change is patch 1, if I can get your Acked-by for
it I will send it via Avi.
--
Hollis Blanchard
IBM Linux Technology Center
^ permalink raw reply
* patches for 2.6.26
From: Kumar Gala @ 2008-04-10 14:21 UTC (permalink / raw)
To: ppc-dev list
Guy's
if you have work you want in 2.6.26 related to Freescale PPC's let me
know. Ideally you can provide links to the patches in http://patchwork.ozlabs.org/linuxppc/
thanks
- k
^ permalink raw reply
* Re: Patches added to powerpc.git powerpc-next and master branches
From: Laurent Pinchart @ 2008-04-10 14:20 UTC (permalink / raw)
To: Kumar Gala; +Cc: linuxppc-dev, paulus
In-Reply-To: <649E760F-1A32-46C3-AB61-8F5249BD1290@kernel.crashing.org>
[-- Attachment #1: Type: text/plain, Size: 352 bytes --]
Hi Kumar,
On Thursday 10 April 2008 16:10, Kumar Gala wrote:
> Laurent,
>
> The cpm/82xx ones should go via me.
Sorry, I didn't know that. I'll e-mail you directly next time.
Best regards,
--
Laurent Pinchart
CSE Semaphore Belgium
Chaussee de Bruxelles, 732A
B-1410 Waterloo
Belgium
T +32 (2) 387 42 59
F +32 (2) 387 42 75
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply
* Re: Patches added to powerpc.git powerpc-next and master branches
From: Kumar Gala @ 2008-04-10 14:11 UTC (permalink / raw)
To: Paul Mackerras; +Cc: linuxppc-dev
In-Reply-To: <18430.2296.189338.485646@cargo.ozlabs.ibm.com>
On Apr 10, 2008, at 7:32 AM, Paul Mackerras wrote:
> Laurent Pinchart writes:
>
>> could you please add the following patches ?
>
> Sure, if Kumar acks them, since they are all 8xxx-related as far as I
> can see (with the exception of the part of 2/5 that adds the new
> dt_get_virtual_reg function). Or Kumar can put them in his tree.
I'll deal with them. There are a larger number of CPM/8xxx related
patches that I need to go through.
- k
^ permalink raw reply
* Re: Patches added to powerpc.git powerpc-next and master branches
From: Kumar Gala @ 2008-04-10 14:10 UTC (permalink / raw)
To: Laurent Pinchart; +Cc: linuxppc-dev, paulus
In-Reply-To: <200804101346.32376.laurentp@cse-semaphore.com>
Laurent,
The cpm/82xx ones should go via me.
- k
On Apr 10, 2008, at 6:46 AM, Laurent Pinchart wrote:
> Hi Paul,
>
> could you please add the following patches ?
>
> [PATCHv4 1/5] cpm_uart: Allocate DPRAM memory for SMC ports on CPM2-
> based
> platforms.
> http://ozlabs.org/pipermail/linuxppc-dev/2008-April/053858.html
>
> [PATCHv4 2/5] powerpc: Add bootwrapper function to get virtual reg
> from the
> device tree.
> http://ozlabs.org/pipermail/linuxppc-dev/2008-April/053859.html
>
> [PATCHv4 3/5] cpm-serial: Relocate CPM buffer descriptors and SMC
> parameter
> ram.
> http://ozlabs.org/pipermail/linuxppc-dev/2008-April/053860.html
>
> [PATCHv4 4/5] ep8248e: Reference SMC parameter RAM base in the
> device tree.
> http://ozlabs.org/pipermail/linuxppc-dev/2008-April/053862.html
>
> [PATCHv4 5/5] cpm2: Reset the CPM when early debugging is not enabled.
> http://ozlabs.org/pipermail/linuxppc-dev/2008-April/053861.html
>
> Thanks.
>
> Best regards,
>
> --
> Laurent Pinchart
> CSE Semaphore Belgium
>
> Chaussee de Bruxelles, 732A
> B-1410 Waterloo
> Belgium
>
> T +32 (2) 387 42 59
> F +32 (2) 387 42 75
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
^ permalink raw reply
* Re: [PATCH] [v5] Add idle wait support for 44x platforms
From: Arnd Bergmann @ 2008-04-10 13:44 UTC (permalink / raw)
To: linuxppc-dev; +Cc: kvm-ppc-devel
In-Reply-To: <df0f79b7b4ab628887c2.1207673354@thinkpadL>
On Tuesday 08 April 2008, Jerone Young wrote:
> +static struct sleep_mode modes[] =3D {
> +=A0=A0=A0=A0=A0=A0=A0{ .name =3D "wait", .entry =3D &ppc44x_idle },
> +=A0=A0=A0=A0=A0=A0=A0{ .name =3D "spin", .entry =3D NULL },
> +};
> +
> +int __init ppc44x_idle_init(void)
> +{
> +=A0=A0=A0=A0=A0=A0=A0void *func =3D modes[current_mode].entry;
> +=A0=A0=A0=A0=A0=A0=A0ppc_md.power_save =3D func;
> +=A0=A0=A0=A0=A0=A0=A0return 0;
> +}
> +
> +arch_initcall(ppc44x_idle_init);
> +
> +static int __init idle_param(char *p)
> +{=20
> +=A0=A0=A0=A0=A0=A0=A0int i;
> +
> +=A0=A0=A0=A0=A0=A0=A0for (i =3D 0; i < ARRAY_SIZE(modes); i++) {
> +=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0if (!strcmp(modes[i].name, =
p)) {
> +=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0cur=
rent_mode =3D i;
> +=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0bre=
ak;
> +=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0}
> +=A0=A0=A0=A0=A0=A0=A0}
> +
> +=A0=A0=A0=A0=A0=A0=A0return 0;
> +}
> +
> +early_param("idle", idle_param);
ok, sorry to steal the show again, now that everyone seems to be happy
with the current code, but isn't this equivalent to the simpler
static int __init idle_param(char *p)
{
if (!strcmp(modes[i].name, "spin"))
ppc_md.power_save =3D NULL;
}
early_param("idle", idle_param);
if you statically initialize the ppc_md.power_save function to ppc44x_idle
in the platform setup files?
Arnd <><
^ permalink raw reply
* Re: State of the MPC5200 PSC AC97 driver
From: Robert Schwebel @ 2008-04-10 13:50 UTC (permalink / raw)
To: Marian Balakowicz; +Cc: linuxppc-dev, Sylvain Munaut, spitzauer_77
In-Reply-To: <47FDEF9B.5000506@semihalf.com>
On Thu, Apr 10, 2008 at 12:44:43PM +0200, Marian Balakowicz wrote:
> Last year you have posted a MPC5200 PSC AC97 driver patch
> "[PATCH 9/9] sound: Add support for Freescale MPC5200 AC97 interface."
> with the following comment:
>
> > Not quite a clean driver, but it get things done (well, mostly).
> > Only included to be able to test functionalityi/usage of
> > the BestComm driver.
>
> There are various FIXMEs and commented out code here and there.
> Could you elaborate a bit on the overall state of the driver's
> functionality,
> which areas need improvement and attention?
>
> Seems that you mainly tested BestComm with this driver, what was the
> overall
> BestComm performance, any issues here? Did you use any specific test setup
> involving some dedicated application, etc.?
>
> Did anyone else tried it and/or has a updated version or can share
> experience?
Sidenote: last time we tried (2.6.23.1), the AC97 driver didn't work,
tested on the phyCORE-MPC5200B-tiny board. No sound, just a little bit
noise which can be muted with the mixer. And music finishes about 7
times as fast as it usually should. So we didn't manage to make it work
yet.
Robert
--
Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
Pengutronix - Linux Solutions for Science and Industry
Handelsregister: Amtsgericht Hildesheim, HRA 2686
Hannoversche Str. 2, 31134 Hildesheim, Germany
Phone: +49-5121-206917-0 | Fax: +49-5121-206917-9
^ permalink raw reply
* Re: [PATCH] [POWERPC] 4xx: Add endpoint support to 4xx PCIe driver
From: Stefan Roese @ 2008-04-10 13:37 UTC (permalink / raw)
To: benh; +Cc: linuxppc-dev
In-Reply-To: <1207830182.6958.11.camel@pasglop>
On Thursday 10 April 2008, Benjamin Herrenschmidt wrote:
> > Understood. But for this "dynamic" root-complex/endpoint configuration as
> > implemented with the current version of the patch, I can't change the
> > PCIe node in the dts from root-complex mode to endpoint mode, since I
> > would loose root-complex functionality. Perhaps I'm missing something
> > here.
>
> Well, I would expect the firmware (ie. uboot) to provide the right
> device-node type...
Now I have to re-check to see what you really have in mind. Do you think about
creating two different PCIe nodes, one for root-complex and one for endpoint
functionality? Or is your idea to add a property to the existing PCIe
device-tree node (like "mode = endpoint"), or perhaps change the device_type
from "pci" to "pci-endpoint"? I would vote for the latter.
Best regards,
Stefan
^ permalink raw reply
* Re: ppc405ep emac driver loading problem
From: M B @ 2008-04-10 13:03 UTC (permalink / raw)
To: Josh Boyer; +Cc: ppc-dev, Stefan Roese
In-Reply-To: <20080410065211.7befbfba@zod.rchland.ibm.com>
On Thu, Apr 10, 2008 at 1:52 PM, Josh Boyer <jwboyer@linux.vnet.ibm.com> wrote:
> You have to call of_platform_bus_probe with the various bus types for
> your board. See the top few functions of:
>
> arch/powerpc/platforms/40x/walnut.c
Well I did this, but I made a typo (plb4 instead of plb3).
So thanks a lot for making me recheck this section. I don't know how
long I would have searched for this else.
Regards
Markus
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox