All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/7 v4] 83xx, kmeter1: add I2C, dtt, eeprom support
Date: Wed, 25 Feb 2009 08:11:18 +0100	[thread overview]
Message-ID: <49A4EF16.4020209@denx.de> (raw)
In-Reply-To: <20090224143740.b8b1e792.kim.phillips@freescale.com>

Hello Kim,

Kim Phillips wrote:
> On Tue, 24 Feb 2009 11:30:34 +0100
> Heiko Schocher <hs@denx.de> wrote:
> 
>> diff --git a/board/keymile/kmeter1/kmeter1.c b/board/keymile/kmeter1/kmeter1.c
>> index f04a57a..a3c58ae 100644
>> --- a/board/keymile/kmeter1/kmeter1.c
>> +++ b/board/keymile/kmeter1/kmeter1.c
>> @@ -59,6 +59,23 @@ const qe_iop_conf_t qe_iop_conf_tab[] = {
>>  	{0,  0, 0, 0, QE_IOP_TAB_END},
>>  };
>>
>> +static int board_init_i2c_busses (void)
>> +{
>> +	I2C_MUX_DEVICE *dev = NULL;
>> +	uchar	*buf;
>> +
>> +	/* Set up the Bus for the DTTs */
>> +	buf = (unsigned char *) getenv ("dtt_bus");
> 
> Heiko, what am I missing here?  I thought any reference to environment
> pollution in the form of "dtt_bus" would have been gone by now.  Did we
> misunderstand each other here?  If its value changes between boards

Yes, I think so ...

> (and not boots), then there is no reason for this to be an environment
> variable.  No?

There is a reason, because if it is an environment variable, we (or better
the board manufacturer) can use one u-boot binary for all variants of
his hardware (as I said, they differ only in the i2c bus topology)

bye
Heiko

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

  reply	other threads:[~2009-02-25  7:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-24 10:30 [U-Boot] [PATCH 2/7 v4] 83xx, kmeter1: add I2C, dtt, eeprom support Heiko Schocher
2009-02-24 20:37 ` Kim Phillips
2009-02-25  7:11   ` Heiko Schocher [this message]
2009-02-26  1:31     ` Kim Phillips

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=49A4EF16.4020209@denx.de \
    --to=hs@denx.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.