From: Boaz Harrosh <bharrosh@panasas.com>
To: thanatos <thanatos@trollprod.org>
Cc: teheo@novell.com, linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: Maybe Sorry for that but where should i write .)
Date: Sun, 30 Dec 2007 13:53:28 +0200 [thread overview]
Message-ID: <477786B8.9040000@panasas.com> (raw)
In-Reply-To: <4775A7D8.6000001@trollprod.org>
On Sat, Dec 29 2007 at 3:50 +0200, thanatos <thanatos@trollprod.org> wrote:
> I got a sata controller ignitio
>
> 00:11.0 SATA controller: Initio Corporation INI-1623 PCI SATA-II
> Controller (rev 02) (prog-if 00 [Vendor specific])
> Subsystem: Initio Corporation INI-1623 PCI SATA-II Controller
> Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 11
> I/O ports at dc00 [size=256]
> I/O ports at d800 [size=256]
> I/O ports at d400 [size=256]
> I/O ports at d000 [size=256]
> I/O ports at cc00 [size=256]
> Memory at cffff000 (32-bit, non-prefetchable) [size=4K]
> Expansion ROM at cff80000 [disabled] [size=256K]
> Capabilities: [dc] Power Management version 2
>
>
> and an "no yet usable" 320 hdd, cause of lba48
>
> ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata3.00: HPA unlocked: 625142448 -> 625142448, native 18446744072354982576
> ata3.00: ATA-8: SAMSUNG HD321KJ, CP100-12, max UDMA7
> ata3.00: 625142448 sectors, multi 0: LBA48 NCQ (depth 0/32)
> ata3.00: ERROR: This driver doesn't support LBA48 yet and may cause
> data corruption on such devices. Disabling.
> ata3.00: disabled
>
> i'm still on kernel 2.6.22. i had look on changelog 2.6.23 and even
> 2.6.24 nothing for that, is theyre a roadmap ?
>
> so if i could help in any way testing patch. i'm theyre
cc: the linux-scsi mailing list.
Personally I have nothing to do with this driver, I only sent a fix
for a patch in 2.6.23
Boaz
next parent reply other threads:[~2007-12-30 11:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4775A7D8.6000001@trollprod.org>
2007-12-30 11:53 ` Boaz Harrosh [this message]
2008-01-02 7:14 ` Maybe Sorry for that but where should i write .) Tejun Heo
2008-01-02 13:54 ` Alan Cox
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=477786B8.9040000@panasas.com \
--to=bharrosh@panasas.com \
--cc=linux-scsi@vger.kernel.org \
--cc=teheo@novell.com \
--cc=thanatos@trollprod.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.