From: Grzegorz Bernacki <gjb@semihalf.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v6] Add support for the digsy MTC board.
Date: Fri, 13 Mar 2009 10:49:54 +0100 [thread overview]
Message-ID: <49BA2C42.5080903@semihalf.com> (raw)
In-Reply-To: <20090312184742.87C12832E8B8@gemini.denx.de>
>> Yes we can, but it is safer this way in the case when ethernet address
>> spans across two chips. Rest of comments addressed in version 7 of the
>> patch which will be sent soon.
>
> Is such a scenario (MAC address split across 2 different EEPROM
> devices) possible (and supported) on these systems?
>
I think it is possible, cause whole eeprom is threated as a one continuous
area. Moreover, this function is called only if ethaddr environment variable
is not set, so not very often. I don't think optimizing it is worth risk of
reading incorrect ethernet address.
regards,
Grzesiek
next prev parent reply other threads:[~2009-03-13 9:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-13 13:53 [U-Boot] [PATCH v6] Add support for the digsy MTC board Grzegorz Bernacki
2009-02-19 11:21 ` Grzegorz Bernacki
2009-03-12 12:56 ` Wolfgang Denk
2009-03-12 15:25 ` Grzegorz Bernacki
2009-03-12 18:47 ` Wolfgang Denk
2009-03-13 9:49 ` Grzegorz Bernacki [this message]
2009-03-13 13:47 ` Wolfgang Denk
2009-03-17 9:05 ` Grzegorz Bernacki
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=49BA2C42.5080903@semihalf.com \
--to=gjb@semihalf.com \
--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