From: Eyal Lebedinsky <eyal@eyal.emu.id.au>
To: list linux-kernel <linux-kernel@vger.kernel.org>
Cc: Roy Sigurd Karlsbakk <roy@karlsbakk.net>,
Andre Hedrick <andre@linux-ide.org>
Subject: Re: 2.4.18: many IDE errors
Date: Mon, 25 Mar 2002 09:24:38 +1100 [thread overview]
Message-ID: <3C9E5226.FD8FAB70@eyal.emu.id.au> (raw)
In-Reply-To: <Pine.LNX.4.30.0203242314350.31118-100000@mustard.heime.net>
Roy Sigurd Karlsbakk wrote:
>
> > The PCI IDE cards I use are ATA-100, so this is the max speed available
> > to be. The four large disks can do ATA-133.
> >
> > The 48bit addressing (to allow >137GB) seems to be unrelated, and it
> > works with these cards. But I needed to apply:
> > http://www.kernel.org/pub/linux/kernel/people/hedrick/ide-2.4.18/
> > ide.2.4.18-rc1.02152002.patch.bz2
>
> but ...
>
> how can that work? i mean - 48bit addressing is in the udma133 standard
> but not in udma100...
>
> how does the /proc/mdstat and /proc/partitions look?
I am not in front of the machine, but let me tell you that mdstat shows
a full 480GB RAID5. There are no partitions (hde/g/i/k are used raw).
Again, I think udma133 and 48bit addressing are two, independent issues.
The first is an electronic spec for the hardware, the second is an api
standard which, it seems, can run at any speed.
Maybe Andre can make a clear statement here?
--
Eyal Lebedinsky (eyal@eyal.emu.id.au) <http://samba.org/eyal/>
next parent reply other threads:[~2002-03-24 22:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.30.0203242314350.31118-100000@mustard.heime.net>
2002-03-24 22:24 ` Eyal Lebedinsky [this message]
2002-03-25 9:22 ` Vojtech Pavlik
2002-03-24 8:03 Eyal Lebedinsky
2002-03-24 8:21 ` Andre Hedrick
2002-03-24 12:27 ` Eyal Lebedinsky
2002-03-24 22:18 ` Vojtech Pavlik
2002-03-25 10:03 ` Andre Hedrick
2002-03-25 10:26 ` Eyal Lebedinsky
2002-03-25 10:32 ` Andre Hedrick
2002-03-25 9:58 ` Eyal Lebedinsky
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=3C9E5226.FD8FAB70@eyal.emu.id.au \
--to=eyal@eyal.emu.id.au \
--cc=andre@linux-ide.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roy@karlsbakk.net \
/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
all inboxes | Powered by JetHome®