mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: b.zolnierkiewicz@elka.pw.edu.pl
Cc: linux-kernel@vger.kernel.org
Subject: LBA48 on PDC20265 (again and again...)
Date: Wed, 3 Sep 2003 14:46:42 +0200	[thread overview]
Message-ID: <BFC117A6765@vcnet.vc.cvut.cz> (raw)

Hi,
  during last year there was couple of complaints that pdc202xx_old
driver does not allow LBA48 on first channel, and couple of confirmations
that just removing these two lines which do:

  if (hwif->pci_dev->device == PCI_DEVICE_ID_PROMISE_20265)
      hwif->no_lba48 = (hwif->channel) ? 0 : 1;
      
fixes problem, and both channels run with lba48 drives just fine...

  Yesterday I bring home two nice 160GB seagates, hooked them up to
the Promise, and booted. And to my surprise we still do not enable
lba48 on primary channel...

  Is there some reason for doing that? I removed this, and I was able
to copy contents of my old 120GB disk to the 160GB one, with 40G offset
(so lba48 has to work, otherwise first 40GB holding an VFAT partition with
some gzipped test files gets corrupted). Currently these two drives
are unused (they just hold backup copy of dying 120GB wd), so I can do
any experiments you may want to confirm/decline idea that we should
remove this no_lba48 hack. Of course unless you have datasheet which says
that it cannot work. But as Promise BIOS happily says that two 149GB disks
(149 * 2^30 == 160 * 10^9) running UDMA5 are attached, I assume that it 
is willing to handle LBA48 on both channels.
                                              Thanks,
                                                  Petr Vandrovec
                                                  


             reply	other threads:[~2003-09-03 12:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-03 12:46 Petr Vandrovec [this message]
2003-09-03 13:20 ` Bartlomiej Zolnierkiewicz
2003-09-03 13:49   ` Bartlomiej Zolnierkiewicz
2003-09-04 17:11     ` Petr Vandrovec

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=BFC117A6765@vcnet.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=b.zolnierkiewicz@elka.pw.edu.pl \
    --cc=linux-kernel@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 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®