linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sylvain Munaut <tnt@246tNt.com>
To: Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: mpc5xxx support (Was: Re: Proposed Kconfig update patch for help text)
Date: Fri, 02 Apr 2004 01:35:58 +0200	[thread overview]
Message-ID: <406CA75E.2070508@246tNt.com> (raw)
In-Reply-To: <20040401161622.GA26876@smtp.west.cox.net>


Hi

>For 2.6, I think one of the following options needs to be done.
>- Motorola code, cleaned up with input from the community (and the bits
>  Linux just doesn't need, left out).
>- Ignore the Motorola code, or since it's GPL (must be to be in the
>  kernel, so I'm just making the assumption here...) use it as a guide
>  for how things work to implement a clean Linux implementation of
>  the code. I know there's someone working on this (who pops up on
>  #mklinux on freenode from time to time) but I don't know how far
>  they've gotten.

I think you're referring to me ;)
What is done :
 - All the kconfig stuff to add options for MPC5xxx and the very low
level stuff like adding in cputable and so on, just to get it recognized.
 - A serial driver that provides a working console ( It still misses
some stuff like modem ctrl because I don't understand that one well )
 - The I2C driver is working ( I can access the on board eeprom of the
IceCube )
 - The USB driver is started however it's not functionnal yet.
Apparently there is a lot of endian issues. In the 2.4 core, they
modified the generic ohci driver with #ifdef #endif to  change the
access from little endian to big endian. But I don't like this solution
because I personnaly have on a custom board a OHCI on PCI and the built
in ports, so I need to find a 'clean' solution.
 - The ethernet code is in *VERY* early stages, I just have the global
arch and some ideas in my head on how to do it.

I'm planning on just ignoring the Motorola code since there apparently
are problem with it ( I though that the motorola update was planned for
mid-feb but ... ) , I was just gonna implement something very simple
that just does what it need for the linux drivers to work cleanly and
properly.

I've tried to write the code as cleany as possible, it uses the OCP
stuff that was on linux-2.5-ocp and also the generic dma stuff.

I can provide the patches on request, I just didn't published it because
I don't know where to ...

Also, for a couple of week, my work is 'paused' on this but since I
would need stuff like ethernet and I2S working for mid-may, I'll resume
my work on it ASAP.

Sylvain Munaut

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2004-04-01 23:35 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-31 22:42 Proposed Kconfig update patch for help text John Whitney
2004-03-31 23:06 ` Wolfgang Denk
2004-04-01  0:04   ` Dan Malek
2004-04-01  0:14   ` John Whitney
2004-04-01  8:35     ` Geert Uytterhoeven
2004-04-01 13:49       ` Kumar Gala
2004-04-01 15:02         ` Wolfgang Denk
2004-04-01 16:16           ` mpc5xxx support (Was: Re: Proposed Kconfig update patch for help text) Tom Rini
2004-04-01 16:58             ` Dan Malek
2004-04-01 17:03               ` Tom Rini
2004-04-01 17:18               ` mpc5xxx support (Was: " Wolfgang Denk
2004-04-01 17:05             ` Wolfgang Denk
2004-04-01 17:19               ` Tom Rini
2004-04-01 18:56                 ` Wolfgang Denk
2004-04-01 19:11                   ` Tom Rini
2004-04-02  0:24               ` mpc5xxx support (Was: " Sylvain Munaut
2004-04-01 23:35             ` Sylvain Munaut [this message]
2004-04-02  2:59               ` New OCP for 2.6 was (Re: mpc5xxx support ) Matt Porter
2004-04-02 16:56               ` mpc5xxx support (Was: Re: Proposed Kconfig update patch for help text) Wolfgang Denk
2004-04-02 17:21                 ` Sylvain Munaut
2004-04-07 14:00                   ` Wolfgang Denk
2004-04-07 14:16                     ` Sylvain Munaut
2004-04-01 15:26         ` Proposed Kconfig update patch for help text Tom Rini
2004-04-01 21:50       ` John Whitney
2004-04-07 14:25         ` Kumar Gala
2004-04-07 15:01         ` 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=406CA75E.2070508@246tNt.com \
    --to=tnt@246tnt.com \
    --cc=linuxppc-dev@lists.linuxppc.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).