linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Scott Wood <scottwood@freescale.com>
Cc: Vitaly Bordug <vitb@kernel.crashing.org>,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
	linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 1/2] [IDE] Platform IDE driver
Date: Wed, 25 Jul 2007 23:35:00 +0400	[thread overview]
Message-ID: <46A7A5E4.4090105@ru.mvista.com> (raw)
In-Reply-To: <46A7A1D5.7020003@freescale.com>

Scott Wood wrote:

>>> It doesn't buy us anything in here, but it's conceivable that someone 
>>> may want to write a driver that uses a shift in the I/O accessor 
>>> rather than an array of port offsets,

>>    It wouldn't be IDE driver then, and neither it would be libata 
>> which also does this another way this (despite pata_platform uses 
>> shifts too -- not in the accessors, so no speed loss).

> The device tree is not just for Linux.

    Yeah, and I can't wait to see some other its users. ;-)
    This doesn't mean that shift is better anyway. If everyone considers it 
better, I give up. But be warned that shift (stride) is not the only property 
characterizing register accesses -- the regs might be only accessible as 
16/32-bit quantities, for example (16-bit is a real world example -- from 
Amiga or smth of that sort, IIRC).

>>> equivalent of the cntlzw innstruction, and shift makes it clear that 
>>> the stride must be power-of-two).  Plus, using shift is consistent 
>>> with what we do on ns16550.

>>    Why the heck should we care about the UART code taling about IDE?!

> Consistency?

    We're not obliged to be consistent with every piece of the kernel code.

> -Scott

MBR, Sergei

  reply	other threads:[~2007-07-25 19:35 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-25 16:53 [PATCH 1/2] [IDE] Platform IDE driver (was: MMIO IDE driver) Vitaly Bordug
2007-07-25 16:53 ` [PATCH 2/2] [POWERPC] MPC8349E-mITX: use platform IDE driver for CF interface Vitaly Bordug
2007-07-25 17:06   ` Sergei Shtylyov
2007-07-25 17:54     ` Sergei Shtylyov
2007-07-25 18:01       ` Scott Wood
2007-07-25 18:19         ` Sergei Shtylyov
2007-07-25 18:39           ` Scott Wood
2007-07-25 19:30             ` Sergei Shtylyov
2007-07-26 16:24               ` Sergei Shtylyov
2007-07-31 22:47             ` Segher Boessenkool
2007-07-25 18:29         ` Sergei Shtylyov
2007-07-25 18:46           ` Scott Wood
2007-07-26 17:21             ` Vitaly Bordug
2007-07-26 17:45               ` Sergei Shtylyov
2007-07-31 22:36       ` Segher Boessenkool
2007-07-31 23:56         ` Alan Cox
2007-08-06 17:19           ` Segher Boessenkool
2007-08-01 13:11         ` Sergei Shtylyov
2007-07-26 17:12     ` Vitaly Bordug
2007-07-25 17:29   ` Scott Wood
2007-07-25 17:43 ` [PATCH 1/2] [IDE] Platform IDE driver (was: MMIO IDE driver) Alan Cox
2007-07-26 19:28   ` Bartlomiej Zolnierkiewicz
2007-07-25 17:59 ` Kumar Gala
2007-07-25 19:00 ` Sergei Shtylyov
2007-07-25 19:05   ` Scott Wood
2007-07-25 19:16     ` Sergei Shtylyov
2007-07-25 19:17       ` [PATCH 1/2] [IDE] Platform IDE driver Scott Wood
2007-07-25 19:35         ` Sergei Shtylyov [this message]
2007-07-31 22:31           ` Segher Boessenkool
2007-08-01 12:39             ` Sergei Shtylyov
2007-08-06 17:16               ` Segher Boessenkool
2007-07-25 19:37 ` [PATCH 1/2] [IDE] Platform IDE driver (was: MMIO IDE driver) Guennadi Liakhovetski
2007-07-25 19:48   ` Sergei Shtylyov
2007-07-25 19:54     ` Guennadi Liakhovetski
2007-07-25 20:01       ` Sergei Shtylyov
2007-07-25 20:09         ` Guennadi Liakhovetski
2007-07-25 20:39   ` Alan Cox
2007-07-26 19:41     ` Guennadi Liakhovetski
2007-07-26 19:52       ` Sergei Shtylyov
2007-07-26 20:13         ` Guennadi Liakhovetski
2007-07-26 20:11       ` Bartlomiej Zolnierkiewicz
2007-07-26 19:28 ` Bartlomiej Zolnierkiewicz

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=46A7A5E4.4090105@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@freescale.com \
    --cc=vitb@kernel.crashing.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).