From: Mark Lord <liml@rtr.ca>
To: Jeff Garzik <jeff@garzik.org>
Cc: Tejun Heo <htejun@gmail.com>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: [PATCH 2.6.22-rc6] sata_inic162x: add big fat warning about broken LBA48 support
Date: Thu, 28 Jun 2007 21:15:26 -0400 [thread overview]
Message-ID: <46845D2E.4050102@rtr.ca> (raw)
In-Reply-To: <4683F626.9040401@garzik.org>
Jeff Garzik wrote:
> Tejun Heo wrote:
>> Jeff Garzik wrote:
>>> Mark Lord wrote:
>>>> Tejun Heo wrote:
>>>>> sata_inic162x can't do LBA48 properly yet. Whine loudly about it to
>>>>> reduce confusion.
>>>> Why not whine only when an affected device is actually present?
>>> That's sorta that I think...
>>
>> That was me being lazy. I'll just ban > LBA28 disks on the controller.
>
> Sounds better to me... I certainly prefer that to clipping-to-1xxGB,
> especially given the shaky state of the overall driver.
I wonder if PIO works for LBA48 on that chipset (very, *very* likely).
Maybe just fall back to PIO for an LBA48 drive.
Or even better, fall back to PIO only for sectors beyond 128GB.
???
Or wait for a more stable driver..
next prev parent reply other threads:[~2007-06-29 1:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-28 16:07 [PATCH 2.6.22-rc6] sata_inic162x: add big fat warning about broken LBA48 support Tejun Heo
2007-06-28 16:14 ` Greg Freemyer
2007-06-28 16:27 ` Tejun Heo
2007-06-28 16:35 ` Alan Cox
2007-06-28 16:59 ` Greg Freemyer
2007-06-28 17:50 ` Mark Lord
2007-06-28 17:51 ` Jeff Garzik
2007-06-28 17:53 ` Tejun Heo
2007-06-28 17:55 ` Jeff Garzik
2007-06-29 1:15 ` Mark Lord [this message]
2007-06-29 1:32 ` Tejun Heo
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=46845D2E.4050102@rtr.ca \
--to=liml@rtr.ca \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.