linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Ric Wheeler <rwheeler@redhat.com>,
	linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org,
	Jim Meyering <jim@meyering.net>,
	linux-kernel@vger.kernel.org, Martin Petersen <mkp@mkp.net>,
	Matt Domsch <Matt_Domsch@Dell.com>
Subject: Re: tools support for non-512 byte sector sizes
Date: Tue, 29 Jul 2008 17:54:03 -0400	[thread overview]
Message-ID: <488F917B.2050800@garzik.org> (raw)
In-Reply-To: <20080729182611.GB24924@parisc-linux.org>

Matthew Wilcox wrote:
> On Tue, Jul 29, 2008 at 01:24:31PM -0400, Ric Wheeler wrote:
>> Jim pinged me about the use case for having our tool chain (parted 
>> specifically) support devices with non-512 bytes sectors.
> 
> Matt Domsch spoke with me about this at OLS.  I took that opportunity,
> and I'll take this one, to pimp my ata-ram driver which allows you to
> alter the sector sizse to whatever you want:
> 
> http://git.kernel.org/?p=linux/kernel/git/willy/misc.git;a=shortlog;h=ata-ram
> 
> I'll admit to having not tested it with anything other than 512, but it
> ought to support 4096 byte sectors just fine.  I haven't looked at what
> would be required to support 520-byte sectors.
> 
> Jeff, any interest in merging ata-ram soon?  I've got some users inside
> Intel, and Zab persuaded me to add the multiple port support last night,
> so it's not just useful for me.  I think it's also a nice template to
> have around to show how to write a minimal libata driver.

I'm happy to include ata_ram whenever it is working and you think it's 
ready for inclusion.

	Jeff




  parent reply	other threads:[~2008-07-29 21:54 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-29 17:24 tools support for non-512 byte sector sizes Ric Wheeler
2008-07-29 18:21 ` Alan Cox
2008-07-29 18:55   ` Matthew Wilcox
2008-07-29 21:07     ` Alan Cox
2008-07-29 18:26 ` Matthew Wilcox
2008-07-29 18:37   ` James Bottomley
2008-07-29 18:42     ` Matthew Wilcox
2008-07-29 18:44       ` James Bottomley
2008-07-29 18:50         ` Matthew Wilcox
2008-07-29 19:00           ` James Bottomley
2008-07-29 18:48     ` Martin K. Petersen
2008-07-29 18:54       ` Ric Wheeler
2008-07-29 18:56         ` James Bottomley
2008-07-29 23:41           ` FUJITA Tomonori
2008-07-30 13:51       ` Matt Domsch
2008-07-30 17:16         ` Jim Meyering
2008-07-30 17:29           ` Matt Domsch
2008-07-30 17:24             ` Alan Cox
2008-07-30 18:13             ` Theodore Tso
2008-07-30 18:28               ` Ric Wheeler
2008-07-30 18:45                 ` Theodore Tso
2008-08-09 13:21             ` Pavel Machek
2008-08-01 16:11         ` Matthew Wilcox
2008-08-05 16:54           ` Matthew Wilcox
2008-08-05 16:57             ` Matthew Wilcox
2008-08-05 16:57           ` Matt Domsch
2008-07-30  5:51     ` Vladislav Bolkhovitin
2008-07-29 18:41   ` Martin K. Petersen
2008-07-29 21:54   ` Jeff Garzik [this message]
2008-07-29 18:43 ` Moore, Eric
2008-07-29 19:03   ` Martin K. Petersen
2008-07-29 19:14     ` Douglas Gilbert

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=488F917B.2050800@garzik.org \
    --to=jeff@garzik.org \
    --cc=Matt_Domsch@Dell.com \
    --cc=jim@meyering.net \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=mkp@mkp.net \
    --cc=rwheeler@redhat.com \
    /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).