linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <stf_xl@wp.pl>
To: Andrew Victor <avictor.za@gmail.com>
Cc: linux-ide@vger.kernel.org, linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [PATCH 3/3 v3] AT91: initialize Compact Flash on AT91SAM9263 cpu
Date: Tue, 17 Feb 2009 11:21:02 +0100	[thread overview]
Message-ID: <200902171121.02329.stf_xl@wp.pl> (raw)
In-Reply-To: <200902121033.57176.stf_xl@wp.pl>

Thursday 12 February 2009 10:33:56 Stanislaw Gruszka napisał(a):
> > Shouldn't this rather be done in the at91_ide driver?
> > I don't want to duplicate it in all the different at91sam9XX_devices.c files.
> 
> Ok, I'll move detection stuff to the driver. Not sure about reset, see my 
> previous mail on this issue. Could we move the reset into driver and
> risk system boot with device which possibly generate interrupts?
> Or perhaps we can remove reset as whole?

I'll finally move resetting stuff into board specific file and detect code
into driver.

> > You could also define two separate "CF type" devices - one for CS4,
> > another for CS5.
> > That would allow for two independent "CF type" interfaces to be used
> > at the same time (see at91sam9260_devices.c in maxim.org.za patches).
> 
> I saw sam9260 code before and I refused idea of doing two CF devices 
> interfaces. AFAIK there are no boards we two CF slots (or separate one
> IDE and one CF slot), are they? I don't think someone really need such 
> board (I could be wrong). If there become a board with two interfaces, 
> then new patch can be done which extend the code.

I see no discussion here is possible :) , ok I'll revrite the code in form like 
at91sam9260_devices.c has.

Cheers
Stanislaw Gruszka

      parent reply	other threads:[~2009-02-17 10:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-09 10:45 [PATCH 3/3 v3] AT91: initialize Compact Flash on AT91SAM9263 cpu Stanislaw Gruszka
2009-02-11 13:59 ` Sergei Shtylyov
2009-02-11 16:46   ` Bartlomiej Zolnierkiewicz
2009-02-11 17:31     ` Sergei Shtylyov
2009-02-12  9:05   ` Stanislaw Gruszka
2009-02-12 16:33     ` Sergei Shtylyov
2009-02-13 10:48       ` Stanislaw Gruszka
2009-02-11 20:03 ` Andrew Victor
2009-02-12  9:33   ` Stanislaw Gruszka
2009-02-13 13:23     ` Sergei Shtylyov
2009-02-17 10:21     ` Stanislaw Gruszka [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=200902171121.02329.stf_xl@wp.pl \
    --to=stf_xl@wp.pl \
    --cc=avictor.za@gmail.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).