linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Stefan Meyer" <reyems@telkomsa.net>
To: "Kumar Gala" <galak@kernel.crashing.org>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Linux kernel for MPC834X platform
Date: Tue, 11 Apr 2006 17:15:30 +0200	[thread overview]
Message-ID: <003101c65d7a$c68fbd60$1100a8c0@stefanlaptop> (raw)
In-Reply-To: 2A229EEE-36CF-4E1D-B94C-D4EB6AB5F5B3@kernel.crashing.org

Hi Kumar
Thanks for the advice. I will rebuild for powerpc and report back.
B.t.w. what is the story behind the ppc and powerpc branches anyway ?

Regards
Stefan

----- Original Message ----- 
From: "Kumar Gala" <galak@kernel.crashing.org>
To: "Stefan Meyer" <reyems@telkomsa.net>
Cc: <linuxppc-embedded@ozlabs.org>
Sent: Tuesday, April 11, 2006 3:03 PM
Subject: Re: Linux kernel for MPC834X platform


> 
> On Apr 11, 2006, at 5:30 AM, Stefan Meyer wrote:
> 
>> Hi All
>> Pardon the intrusion if this is not the correct way to get the  
>> relevant information, but I am relatively new to kernel hacking.
>> Anyway here goes my question:
>> I am getting a Freescale MPC8343 based board up and running and  
>> have been using the BSP (with patched 2.6.11 kernel) release by  
>> Freescale with great success.
>> However when I tried to use the USB ISO transactions it seems to be  
>> non functional. I have connected a known good working codec (tested  
>> on my PC's usb) and tried to access it via the low level sound  
>> driver (/dev/dsp) but it only creates garbled noise.
>> In the meanwhile, I have noticed that the official kernel release  
>> 2.6.17 also start supporting the MPC834X platform and would rather  
>> like to persue that avenue to get my problems addressed (hopefully).
>> I have downloaded the latest 2.6.17 kernel and got it going  with  
>> the configuration for MPC834x_sys, with relation to booting and  
>> ethernet comms.
>> However there are clearly no provision in the USB driver for  
>> setting up the usb clocks and ports (which is of course MPC834x  
>> specific).
>> I have tried to hack it by inserting approriate code form the  
>> 2.6.11 freescale kernel but with very little success.
>> On inspection of the 2.6.11 kernel from Freescale I have also  
>> noticed that the USB core drivers were heavily modified around DMA  
>> buffer management, although the 2.6.17 had no such hacks in place.
>> My question simply relates to the status of the MPC834x  
>> implementation on the 2.6.17 kernel in so far that it is  
>> operational and being tested on hardware platforms. Could you  
>> please direct me to the persons(s) who have experience with this  
>> platform ?
> 
> The USB support for MPC834x only exists if you build it for  
> ARCH=powerpc.  There is a patch on the list archives for adding  
> support to ARCH=ppc.  I don't know if there is any issue with ISO  
> transactions in those version, but they been shown to work with USB  
> ethernet and USB HD devices.
> 
> - kumar
>

  reply	other threads:[~2006-04-11 15:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-11 10:30 Linux kernel for MPC834X platform Stefan Meyer
2006-04-11 13:03 ` Kumar Gala
2006-04-11 15:15   ` Stefan Meyer [this message]
2006-04-11 15:14     ` Kumar Gala
2006-04-11 15:24       ` Stefan Meyer
2006-04-11 15:23         ` Kumar Gala

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='003101c65d7a$c68fbd60$1100a8c0@stefanlaptop' \
    --to=reyems@telkomsa.net \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-embedded@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).