From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [BUG] arch/sh/include/mach-common/mach/sh7785lcr.h: PCA9564_ADDR is 29bit-only
Date: Thu, 27 Aug 2009 04:15:04 +0000 [thread overview]
Message-ID: <20090827041504.GC696@linux-sh.org> (raw)
In-Reply-To: <4A95800A.7020603@gentoo.org>
On Thu, Aug 27, 2009 at 12:01:03PM +0900, yoshii.takashi@renesas.com wrote:
> Oh, sorry.
> This might be because the board I sent you was a special version.
> You (and possibly others who use this version) should revert that commit.
> I'm really sorry for inconvenient.
>
> Paul, are there any good way to support this kind of small differences?
> Is it ok to add configuration menu item like below?
>
Presumably we can figure the version out from the FPGA? If so, we can
just figure out which devices to register, and have different devices for
different versions.
If we can't figure it out from the FPGA, then the next best bet is to use
the mach types, the version information can be encoded in a new
mach-type, and we can simply have a mach_is_xxx() check for determining
the board version and doing the appropriate fixups. We already do this
today for some boards (highlander, r2d, etc.).
next prev parent reply other threads:[~2009-08-27 4:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 18:33 [BUG] arch/sh/include/mach-common/mach/sh7785lcr.h: PCA9564_ADDR Raúl Porcel
2009-08-27 2:39 ` [BUG] arch/sh/include/mach-common/mach/sh7785lcr.h: PCA9564_ADDR is 29bit-only Paul Mundt
2009-08-27 3:01 ` [BUG] arch/sh/include/mach-common/mach/sh7785lcr.h: yoshii.takashi
2009-08-27 4:15 ` Paul Mundt [this message]
2009-08-27 13:57 ` [BUG] arch/sh/include/mach-common/mach/sh7785lcr.h: PCA9564_ADDR Yoshihiro Shimoda
2009-08-27 14:20 ` Raúl Porcel
2009-08-27 14:26 ` [BUG] arch/sh/include/mach-common/mach/sh7785lcr.h: PCA9564_ADDR is 29bit-only Paul Mundt
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=20090827041504.GC696@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.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