mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Larry Hileman <LHileman@snapappliance.com>
To: "'Tomas Szepe'" <szepe@pinerecords.com>,
	Larry Hileman <LHileman@snapappliance.com>
Cc: linux-kernel@vger.kernel.org
Subject: RE: Question about 48 bit IDE on 2.4.18 kernel
Date: Fri, 14 Feb 2003 09:51:06 -0800	[thread overview]
Message-ID: <057889C7F1E5D61193620002A537E8690B5A2D@NCBDC> (raw)

I was asked to figure a way to get us over the 137G barrier on
the 2.4.18 kernel.  Going to 2.4.20/21 can be done in parallel
and I will explain this.

Moving to 2.4.20/21 is a large effort here.  If I need to implement
the larger drives in 2.4.18, I'd like to make sure that this
has not already been done and that I have the latest code.


-----Original Message-----
From: Tomas Szepe [mailto:szepe@pinerecords.com]
Sent: Friday, February 14, 2003 9:43 AM
To: Larry Hileman
Cc: linux-kernel@vger.kernel.org
Subject: Re: Question about 48 bit IDE on 2.4.18 kernel


> [LHileman@snapappliance.com]
> 
> Ok, from this information it would seem that the 2.4.18 kernel
> will not support > 137G drives?  

Is there any reason why you couldn't upgrade to 2.4.20?

-- 
Tomas Szepe <szepe@pinerecords.com>

             reply	other threads:[~2003-02-14 17:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-14 17:51 Larry Hileman [this message]
2003-02-14 18:03 ` Tomas Szepe
  -- strict thread matches above, loose matches on Subject: below --
2003-02-14 17:35 Larry Hileman
2003-02-14 17:43 ` Tomas Szepe
2003-02-13 23:51 Larry Hileman
2003-02-14  1:59 ` Alan Cox
2003-02-14  6:32 ` Andre Hedrick
2003-02-13 23:27 Larry Hileman
2003-02-14  0:47 ` 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=057889C7F1E5D61193620002A537E8690B5A2D@NCBDC \
    --to=lhileman@snapappliance.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=szepe@pinerecords.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

all inboxes | Powered by JetHome®