From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Andrew Victor <avictor.za@gmail.com>
Cc: Stanislaw Gruszka <stf_xl@wp.pl>,
linux-ide@vger.kernel.org, Andrew Victor <linux@maxim.org.za>,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [PATCH 3/3] AT91: initialize IDE driver on AT91SAM9263 cpu
Date: Thu, 05 Feb 2009 23:01:47 +0300 [thread overview]
Message-ID: <498B45AB.3070409@ru.mvista.com> (raw)
In-Reply-To: <cd73a99e0902051143m755cf077le11f01bd4454b15f@mail.gmail.com>
Andrew Victor wrote:
>>>http://download.ronetix.info/sk-eb926x/linux/kernel/2.6.28/003_linux-2.6.28-at91-ronetix-12012009.patch
>> This patch is clearly incomplete because drivers/pcmcia/at91_cf.c does
>>accesses AT91RM9200 specific SMC register, but the patch does nothing about
>>making this work on AT91SAM9. Though it indeed seems that AT91SAM9 can be
>>supported by that driver with minimum change -- perhaps by using
>>cpi_is_*()...
> Rather see latest patch on http://maxim.org.za/at91_26.html.
> The cpu_is_XX() is for run-time selection (and is the preferred mechanism).
> Unfortunately the SMC registers are significantly different on the
> SAM9 and RM9200, so we need to use #ifdefs for compile-time selection.
Ah, seeing the real issue now: different encoding of the DBW fields b/w
those 2 types of SMCs. Oh, and I've missed the different DBW field positions
too... That however can be addressed by using the driver local #define', not
the ones from the headers (which should be conflicting)...
> Regards,
> Andrew Victor
WBR, Sergei
next prev parent reply other threads:[~2009-02-05 20:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 10:47 [PATCH 3/3] AT91: initialize IDE driver on AT91SAM9263 cpu Stanislaw Gruszka
2009-02-03 20:27 ` Andrew Victor
2009-02-04 9:36 ` Stanislaw Gruszka
2009-02-05 12:03 ` Sergei Shtylyov
2009-02-05 19:43 ` Andrew Victor
2009-02-05 20:01 ` Sergei Shtylyov [this message]
2009-02-05 23:52 ` Sergei Shtylyov
2009-02-05 15:06 ` Stanislaw Gruszka
2009-02-04 12:18 ` Sergei Shtylyov
2009-02-04 14:15 ` Stanislaw Gruszka
2009-02-04 15:46 ` Sergei Shtylyov
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=498B45AB.3070409@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=avictor.za@gmail.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=linux@maxim.org.za \
--cc=stf_xl@wp.pl \
/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).