mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Charles R. Anderson" <cra@WPI.EDU>
To: linux-kernel@vger.kernel.org
Subject: 2.4.19-rc3-ac3 ide_map_buffer/ide_unmap_buffer
Date: Thu, 25 Jul 2002 19:38:06 -0400	[thread overview]
Message-ID: <20020725193806.U7778@angus.ind.WPI.EDU> (raw)

[I'm not subscribed, so please Cc: me directly.  Thanks.]

patch-2.4.19-rc3-ac3 has this stuff related to highmem support:

 /*
+ * mapping stuff, prepare for highmem...
+ * 
+ * temporarily mapping a (possible) highmem bio for PIO transfer
+ */
+#define ide_rq_offset(rq) \
+       (((rq)->hard_cur_sectors - (rq)->current_nr_sectors) << 9)
+
+extern inline void *ide_map_buffer(struct request *rq, unsigned long
*flags)
+{
+       return rq->buffer + ide_rq_offset(rq);
+}
+
+extern inline void ide_unmap_buffer(char *buffer, unsigned long *flags)
+{
+       do { } while (0);
+}

Red Hat's 2.4.18-5 kernel has these conflicting bits in
linux-2.4.17-blockhighmem.patch:

+
+/*
+ * temporarily mapping a (possible) highmem bio
+ */
+#define ide_rq_offset(rq) (((rq)->hard_cur_sectors - (rq)->current_nr_sectors) << 9)
+
+extern inline void *ide_map_buffer(struct request *rq, unsigned long
*flags)
+{
+       return bh_kmap_irq(rq->bh, flags) + ide_rq_offset(rq);
+}
+
+extern inline void ide_unmap_buffer(char *buffer, unsigned long *flags)
+{
+       bh_kunmap_irq(buffer, flags);
+}

Which one should I apply? I'm inclined to keep the Red Hat bits, since
the ac3 ide_unmap_buffer does nothing.

[For anyone wondering, I have a new Dell with an Intel 845G chipset for
which I would like DMA support, etc.  I'm attempting to merge
2.4.19-rc3-ac3 with Red Hat's patches.  If anyone has a simple patch for
82801DB IDE DMA support which applies to 2.4.18 I'd be much obliged.]

Thanks.

-- 
Charles R. Anderson <cra@wpi.edu> / http://angus.ind.wpi.edu/~cra/
PGP Key ID: 49BB5886
Fingerprint: EBA3 A106 7C93 FA07 8E15  3AC2 C367 A0F9 49BB 5886

             reply	other threads:[~2002-07-25 23:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-25 23:38 Charles R. Anderson [this message]
2002-07-25 23:45 ` Andre Hedrick
2002-07-26 10:41 ` 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=20020725193806.U7778@angus.ind.WPI.EDU \
    --to=cra@wpi.edu \
    --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®