From: camhirundo@gmail.com (Hirundo Cam)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] kirkwood: add dir-665 support
Date: Thu, 5 May 2011 08:20:27 +0800 [thread overview]
Message-ID: <BANLkTikhFn--4WVGjATZL=0cCiz8qmo=jw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTim6J-wpp+=xsaaxwjmr4XLe-Aa8KA@mail.gmail.com>
Hi Saeed and Nicolas,
2011/5/4 saeed bishara <saeed.bishara@gmail.com>:
> On Wed, May 4, 2011 at 11:16 AM, Simon Guinot <simon@sequanux.org> wrote:
>> Hi Hirundo,
>>
>> On Wed, May 04, 2011 at 04:05:46PM +0800, Hirundo Cam wrote:
>>> This patch is a hack to dir-665 by referencing mv88f6281gtw_ge board.
>>> LEDs, GPIO, Buttons remains unknown.
> Hirundo,
> ? if this board is very similar to mv88f6281gtw_ge, you should use
> the same board setup file. it will be great if you specify the
> differences between the two boards.
I have no mv88f6281gtw_ge board on hand.
However, After I've looked into the setup file of mv88f6281gtw_ge.
I've found that the NOR flash, ddr2 DRAM, switch chip, ethernet port define
are differ from mv88f6281gtw_ge.
I have no idea if we could use #if define to distinguish the different
boards use
the same SoC. While I want also made this adaptable in OpenWrt.
> ? please have a look at sheevaplug-setup.c to see how multiple boards
> supported in same setup file.
> saeed
>
Hum, I think Kernel will rely on the mach-type ID in u-boot to check
which board is in booting. If the original u-boot has changed
mach-type ID, I don't think us the same configuration file with
mv88f6281gtw_ge is good. At least I've tried kernel image compiled
with mv88f6281gtw_ge option but it seems kernel cannot be booted and
hanged in very early stage. Just like the mach-type ID doesn't match.
Regards,
Hirundo Cam
next prev parent reply other threads:[~2011-05-05 0:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 16:34 [PATCH] kirkwood: add dir-665 support Hirundo Cam
2011-04-27 23:52 ` Hirundo Cam
2011-05-03 15:55 ` Hirundo Cam
2011-05-03 20:51 ` mike at compulab.co.il
2011-05-04 2:36 ` Hirundo Cam
2011-05-04 2:54 ` Hirundo Cam
2011-05-04 3:00 ` Hirundo Cam
2011-05-04 6:32 ` Mike Rapoport
2011-05-04 8:09 ` Simon Guinot
2011-05-04 13:51 ` Nicolas Pitre
2011-05-05 0:23 ` Hirundo Cam
2011-05-05 15:06 ` Simon Guinot
2011-05-05 19:55 ` Nicolas Pitre
2011-05-06 15:41 ` Simon Guinot
2011-05-06 20:59 ` Nicolas Pitre
2011-05-04 3:30 ` Hirundo Cam
2011-05-04 6:31 ` Mike Rapoport
2011-05-03 21:14 ` Simon Guinot
[not found] ` <1304496346-13557-1-git-send-email-camhirundo@gmail.com>
2011-05-04 7:56 ` [PATCH v2] " Hirundo Cam
2011-05-04 8:16 ` Simon Guinot
2011-05-04 9:50 ` saeed bishara
2011-05-05 0:20 ` Hirundo Cam [this message]
2011-05-05 7:08 ` saeed bishara
2011-05-05 15:20 ` Hirundo Cam
2011-05-05 0:11 ` Hirundo Cam
2011-05-05 7:50 ` Simon Guinot
2011-05-04 9:23 ` [PATCH] " Jean-Christophe PLAGNIOL-VILLARD
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='BANLkTikhFn--4WVGjATZL=0cCiz8qmo=jw@mail.gmail.com' \
--to=camhirundo@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).