Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@enix.org>
To: linux-mips@linux-mips.org
Subject: Re: kernel for custom MV64341 board?
Date: Wed, 16 Feb 2005 09:57:57 +0100	[thread overview]
Message-ID: <42130B15.8090200@enix.org> (raw)
In-Reply-To: <ubrale09l.fsf@noon.org>

[-- Attachment #1: Type: text/plain, Size: 1623 bytes --]

Hello,

Fredrik a écrit :

> So far I've been using an old 2.4 kernel I used for some Ocelot-G
> work, just to get past the TFTP-load stage. MY QUESTION IS: What would
> be the best kernel version for me to now start customizing for my
> board?  Is 2.6 too bleeding-edge, 2.4 too moldy, or what?  Dealing
> with the MV64341 will be most of the effort, of course.

I have recently hacked a 2.6 Linux-MIPS kernel for a custom RM9000 / 
MV64340 board, and it worked pretty well.

For the MV64340 UART, you can find a driver in the Bitkeeper PowerPC 
tree available at Montavista. Otherwise, I have written an other driver, 
much smaller, but maybe less functionnal than the one available from 
Montavista.

> The Ocelot boards seem well supported, but there looks to be a lot of
> code that would have to change (different system controller, different
> memory map--though I'm flexible--a lot of assumptions about the
> goodies available on-board, etc.).  This is the first time I'll be
> porting the kernel, so it might be more productive for me to start
> from a minimalist configuration and add-in what I need.  Enough code
> to set up the memory configuration would be a big help.

Have a look at Linux-MIPS Wiki (http://www.linux-mips.org) it contains 
an updated version of the MIPS porting guide from Jun Sun. It's a very 
good starting point in my opinion.

Thomas
-- 
PETAZZONI Thomas - thomas.petazzoni@enix.org
http://thomas.enix.org - Jabber: thomas.petazzoni@jabber.dk
http://kos.enix.org, http://sos.enix.org
Fingerprint : 0BE1 4CF3 CEA4 AC9D CC6E  1624 F653 CB30 98D3 F7A7


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

  parent reply	other threads:[~2005-02-16  8:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-16  1:55 kernel for custom MV64341 board? Fredrik
2005-02-16  1:55 ` Fredrik
2005-02-16  8:57 ` Thomas Petazzoni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-02-16  5:05 Brad Larson
2005-02-16  6:37 ` Manish Lachwani
2005-02-16 19:40   ` Fredrik
2005-02-17  9:24     ` Thomas Petazzoni

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=42130B15.8090200@enix.org \
    --to=thomas.petazzoni@enix.org \
    --cc=linux-mips@linux-mips.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