lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Tue, 2 Dec 2008 08:36:25 -0500
From:	"David Ellingsworth" <david@...ntd.dyndns.org>
To:	"Alan Cox" <alan@...rguk.ukuu.org.uk>
Cc:	"Mikael Pettersson" <mikpe@...uu.se>, linux-ide@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: Promise PDC20376

On Tue, Dec 2, 2008 at 5:50 AM, Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
>> A small update to this. It seems the above mentioned interrupt fails
>> somewhere around the 128GB boundary. Interrupt 13h, AH=42 uses a 64
>> bit sector address and should be capable of addressing the entire
>> drive. For a SATA controller, this limitation seems relatively
>> arbitrary. For IDE controllers, a limitation such as this is
>> apparently common.
>
> 137GB I would imagine. That is the point at which LBA48 commands must be
> used not LBA28 and presumably their BIOS code only supports old format
> commands
>

Right, with LBA28 addressing you get 2^28 sector addresses = 2^27 KiB
= 2^17 MiB = 2^7 GiB = 128 GiB which is approximately 137GB. When I
wrote 128GB I really meant 128 GiB.

Regards,

David Ellingsworth

P.S. I hate the "new" binary size notations they only cause confusion.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ