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: Tue, 17 Mar 2009 10:05:43 +0100 [thread overview]
Message-ID: <49BF67E7.9030701@semihalf.com> (raw)
In-Reply-To: <20090313134738.01897832E8B8@gemini.denx.de>
Wolfgang Denk wrote:
> Dear Grzegorz Bernacki,
>
> In message <49BA2C42.5080903@semihalf.com> you wrote:
>>> 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.
>
> You mean, there is actually only *one* phyical EEPROM chip on the
> board? Then the I2C driver is supposed to support reading / writing
> accross page boundaries.
>
Yes, it is one physical chip divided into 4 blocks. The chip is organized
so that accessing different blocks requires using different i2c slave
addresses, effectively making the chip appear as several i2c slaves.
The logic to handle such addressing is already implemented in the eeprom
access functions in the common/cmd_eeprom.c. Next version of the patch
will just use that existing read method.
regards,
Grzesiek
prev parent reply other threads:[~2009-03-17 9:05 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
2009-03-13 13:47 ` Wolfgang Denk
2009-03-17 9:05 ` Grzegorz Bernacki [this message]
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=49BF67E7.9030701@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