From: Fredrik <fcn-sub@noon.org>
To: <linux-mips@linux-mips.org>
Subject: kernel for custom MV64341 board?
Date: Tue, 15 Feb 2005 17:55:50 -0800 [thread overview]
Message-ID: <ubrale09l.fsf@noon.org> (raw)
Howdy,
I'm getting a custom board going: it sports an RM7000 and Marvell
MV64341 system controller (alas, no external UART!). I've hacked
U-Boot to the point where I can TFTP a kernel image and (start to)
boot it.
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.
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.
Suggestions?
/Fredrik
+----------------------------------------------------------------+
| Fredrik Noon, Senior Software Engineer |
| Hifn, Inc. www.hifn.com |
| fnoon@hifn.com +1 408 399 3630 |
|-------------------+--------------------------------------------|
| pgp key: <http://noon.org/keys/pgpkey.txt> 7840AC55 |
+----------------------------------------------------------------+
WARNING: multiple messages have this Message-ID (diff)
From: Fredrik <fcn-sub@noon.org>
To: linux-mips@linux-mips.org
Subject: kernel for custom MV64341 board?
Date: Tue, 15 Feb 2005 17:55:50 -0800 [thread overview]
Message-ID: <ubrale09l.fsf@noon.org> (raw)
Message-ID: <20050216015550.KGQWHa-y7ZACj-g_oAudD9tqgzM0oI86LAFlHUPj7Sc@z> (raw)
Howdy,
I'm getting a custom board going: it sports an RM7000 and Marvell
MV64341 system controller (alas, no external UART!). I've hacked
U-Boot to the point where I can TFTP a kernel image and (start to)
boot it.
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.
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.
Suggestions?
/Fredrik
+----------------------------------------------------------------+
| Fredrik Noon, Senior Software Engineer |
| Hifn, Inc. www.hifn.com |
| fnoon@hifn.com +1 408 399 3630 |
|-------------------+--------------------------------------------|
| pgp key: <http://noon.org/keys/pgpkey.txt> 7840AC55 |
+----------------------------------------------------------------+
next reply other threads:[~2005-02-16 1:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 1:55 Fredrik [this message]
2005-02-16 1:55 ` kernel for custom MV64341 board? Fredrik
2005-02-16 8:57 ` Thomas Petazzoni
-- 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=ubrale09l.fsf@noon.org \
--to=fcn-sub@noon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.