From: Daniel Gorsulowski <Daniel.Gorsulowski@esd.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/1] at91: Update MEESC board support
Date: Wed, 09 Sep 2009 09:15:20 +0200 [thread overview]
Message-ID: <4AA75608.6090207@esd.eu> (raw)
In-Reply-To: <4AA4B599.7090609@esd.eu>
Hello,
Daniel Gorsulowski wrote:
> Hello Wolfgang, Jean-Christophe,
>
> Wolfgang Denk wrote:
>> Dear Daniel,
>>
>> In message <20090904211358.GR30118@game.jcrosoft.org> Jean-Christophe wrote:
>>>> +#ifdef CONFIG_REVISION_TAG
>>>> +u32 get_board_rev(void)
>>>> +{
>>>> + return hw_rev | 0x100;
>>>> +}
>>>> +#endif
>>>> +
>>>> +int misc_init_r(void)
>>>> +{
>>>> +#ifdef CONFIG_MACB
>>>> + u32 hwaddr_btm;
>>>> + u16 hwaddr_top;
>>>> + u8 mac[6];
>>>> +
>>>> + /* Set ethernet address */
>>>> + if (!eth_getenv_enetaddr("ethaddr", mac)) {
>>>> + puts("Missing environment variable 'ethaddr'\n");
>>>> + } else {
>>>> + hwaddr_btm = mac[0] | mac[1] << 8 | mac[2] << 16 | mac[3] << 24;
>>>> + hwaddr_top = mac[4] | mac[5] << 8;
>>>> + writel(hwaddr_btm, (void *)(AT91SAM9263_BASE_EMAC + MACB_SA1B));
>>>> + writel(hwaddr_top, (void *)(AT91SAM9263_BASE_EMAC + MACB_SA1T));
>>> nack this will be done when u-boot will need to use the macb#
> Just imagine: U-boot boots a Linux kernel from NAND flash. It does NOT need the
> ethernet interface, so it does NOT initialize ethernet, so the ethernet address
> will NOT be written to the EMAC module!
> As a result, Linux will assign a random address, that is not acceptable!
>> Jean-Christophe means: The Etherent interface must not be always
>> initialized, but only when it is needed and used within U-Boot itself,
>> i. e. if U-boot is performing anetwork command. See also item 2 at
>> http://www.denx.de/wiki/U-Boot/DesignPrinciples and
>> http://www.denx.de/wiki/view/DULG/EthernetDoesNotWorkInLinux
>>
>> Best regards,
>>
>> Wolfgang Denk
>>
> I know about it.
>
> But this patch does NOT initialize the Ethernet Interface. It JUST write
> the ethernet address to the EMAC module!
>
> So please ACK this patch.
>
>
> Regards,
> Daniel Gorsulowski
it was worth an attempt...
I made a new patch without the MACB stuff, see separate mail.
Now I parse the ethaddr through the kernel commandline. The kernel patch is
temporary available at http://paste.debian.net/46114/ (maybe someone is
interested in it)
Regards,
Daniel Gorsulowski
next prev parent reply other threads:[~2009-09-09 7:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 12:29 [U-Boot] [PATCH 1/1] at91: Update MEESC board support Daniel Gorsulowski
2009-09-04 21:13 ` Jean-Christophe PLAGNIOL-VILLARD
2009-09-04 22:02 ` Wolfgang Denk
2009-09-07 7:26 ` Daniel Gorsulowski
2009-09-07 7:44 ` Simon Kagstrom
2009-09-09 7:15 ` Daniel Gorsulowski [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-09 7:15 Daniel Gorsulowski
2009-09-09 8:58 ` Wolfgang Denk
2009-09-10 14:07 ` Daniel Gorsulowski
2009-09-10 18:41 ` Wolfgang Denk
2009-09-11 7:03 ` Daniel Gorsulowski
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=4AA75608.6090207@esd.eu \
--to=daniel.gorsulowski@esd.eu \
--cc=u-boot@lists.denx.de \
/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