From: Grant Likely <grant.likely@secretlab.ca>
To: Grzegorz Bernacki <gjb@semihalf.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Add support for the digsy MTC board.
Date: Mon, 2 Feb 2009 08:00:20 -0700 [thread overview]
Message-ID: <fa686aa40902020700m4c868246l8ef7296d7a176e@mail.gmail.com> (raw)
In-Reply-To: <4986EC33.9000600@semihalf.com>
On Mon, Feb 2, 2009 at 5:50 AM, Grzegorz Bernacki <gjb@semihalf.com> wrote:
> Grant Likely wrote:
>>> diff --git a/arch/powerpc/configs/52xx/digsy_mtc_defconfig b/arch/powerpc/configs/52xx/digsy_mtc_defconfig
>>> new file mode 100644
>>> index 0000000..ad70d5b
>>> --- /dev/null
>>> +++ b/arch/powerpc/configs/52xx/digsy_mtc_defconfig
>
> I would like to have support for following devices in defconfig for digsy:
> - LXT PHY
> - RTC DS1337
> - EEPROM AT24
> - MTD partitioning based on OF description
>
> If you dont mind I can add them to generic mpc5200 defconfig, otherwise
> I think that separate defconfig is needed.
No problem, go ahead.
>> Do you *really* need your own defconfig for the digsy_mtc. I've
>> grudgingly accepted them for other boards under the argument that the
>> defconfig reflects a specific application of the board. However, I'd
>> much rather see the digsy added to the multiplatform
>> mpc5200_defconfig, especially considering that the MTC looks like it's
>> supposed to be a general purpose platform.
>
>> There is a lot of direct copy/paste from the lite5200.c board file,
>> but the big scary warning comment about not duplicating this code was
>> deleted in the copy (so I know you saw it). Is Semihalf responsible
>> for the U-Boot port to the digsy-mtc? If so then please fix the
>> port_config and clock settings in u-boot.
>>
>
> I will update port config and clock settings in u-boot and use mpc5200_simple
> instead of creating a new file for digsy.
>
> BTW,
> I noticed that there are some problems with mounting file system
> over NFS on Linux-2.6.29-rc3, I see following messages:
> ...
> [ 339.813807] nfs: server 192.168.1.1 not responding, still trying
> [ 339.832144] nfs: server 192.168.1.1 OK
> ...
>
> I haven't noticed in on Linux-2.6.29-rc2. Is there any known problem?
Hmm, I've not seen that problem, but I'll look out for it.
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2009-02-02 15:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 15:33 [PATCH] Add support for the digsy MTC board Grzegorz Bernacki
2009-01-30 16:59 ` Grant Likely
2009-02-02 12:50 ` Grzegorz Bernacki
2009-02-02 15:00 ` Grant Likely [this message]
2009-02-02 16:11 ` Sean MacLennan
2009-02-02 16:44 ` Grzegorz Bernacki
2009-02-02 16:52 ` Sean MacLennan
2009-02-02 16:17 ` Andre Schwarz
2009-02-02 16:42 ` Grzegorz Bernacki
2009-02-02 23:58 ` Wolfgang Denk
2009-02-03 0:05 ` Grant Likely
2009-02-03 8:04 ` Grzegorz Bernacki
2009-02-03 11:08 ` Andre Schwarz
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=fa686aa40902020700m4c868246l8ef7296d7a176e@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=gjb@semihalf.com \
--cc=linuxppc-dev@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).