From: alex@digriz.org.uk (Alexander Clouter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] ARM: Enable TS-78XX features in unknown revisions
Date: Sat, 5 Mar 2011 10:32:18 +0000 [thread overview]
Message-ID: <bbf948-iel.ln1@chipmunk.wormnet.eu> (raw)
Hi,
In gmane.linux.kernel Michael Spang <mspang@csclub.uwaterloo.ca> wrote:
>
> When the manufacturer increases the revision number the platform
> devices for the RTC, NAND, and RNG disappear. We should assume
> new revisions have these devices instead of assuming they do not.
>
NACK
This would break things for anyone running a custom FPGA bitstream (and
they are out there) . The RTC and RNG are possibly the only things that
are able to be implemented in a custom FPGA, the NAND is wholly TS
specific..
Please could you refrain submitting patches for TS-7800 without having
a quick look at:
* http://git.kernel.org/?p=linux/kernel/git/nico/orion.git
* http://www.digriz.org.uk/ts78xx/kernel
The former is pretty much what you have to base all your patches on so
you should be tracking it (which would have solved the re-inventing the
revision update patch), whilst the latter would help tell you things
that have already been done elsewhere.
The latter site also includes thoughts on where the platform code is
going. So far as *zero* people have ever provided feedback or thoughts
(unfortunately they seem too busy just bluntly hammering things in the
ts7000 forum) I have so far to date only done things that I feel are
most appropriate. This includes things like the doorbell code necessary
to get IRQ's firing from the PC/104 bus...which I hope no-one is wasting
their time re-implementing?
This is not a case of megalomania, it's a case of saving wasted effort,
testing patches and getting obtaining code review.
I can see the value in this particular patch, but problems with it could
have trivially been avoided by reworking the FPGA ID code so that the
RTC/NAND/RNG are only enabled when the *magic* is set to 0x00b480; then
we should remove the all the 'case TS7800_REV_1..9' bits. I'll put this
together and push it to Nico, reverting your efforts... :-/
Cheers
[1] http://git.wormnet.eu/?p=alex/ts78xx.git;a=commitdiff;h=de3a91588ccc5f9443f0e0a1656a94c6ddb19bdb
--
Alexander Clouter
.sigmonster says: It's not the fall that kills you, it's the landing.
next reply other threads:[~2011-03-05 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-05 10:32 Alexander Clouter [this message]
2011-03-05 20:05 ` [PATCH v2 2/2] ARM: Enable TS-78XX features in unknown revisions Nicolas Pitre
2011-03-05 21:32 ` Michael Spang
-- strict thread matches above, loose matches on Subject: below --
2011-03-05 4:39 [PATCH " Michael Spang
2011-03-05 4:50 ` [PATCH v2 " Michael Spang
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=bbf948-iel.ln1@chipmunk.wormnet.eu \
--to=alex@digriz.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).