All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@linuxcare.com>
To: dalecki@evision-ventures.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] megaraid driver update for 2.4.0-test10
Date: 19 Nov 2000 22:28:44 +0100	[thread overview]
Message-ID: <d3zoivtzw3.fsf@lxplus015.cern.ch> (raw)
In-Reply-To: <3A170A06.934405FC@evision-ventures.com>
In-Reply-To: dalecki's message of "Sun, 19 Nov 2000 00:00:23 +0100"

>>>>> "dalecki" == dalecki  <dalecki@evision-ventures.com> writes:

A few questions after scanning through your patch, it's likely I
missed something but I am kind acurious.

dalecki> The attached patch does the following: 1. Merge the most
dalecki> current version (aka: 1.08) of the MegaRAID driver from AMI
dalecki> in to the most current kernel (2.4.0-test10 and friends).

Hmmm I don't get it why you changed the return type of the
readl/writel macros to return unsigned long rather than u32 - is there
a reason for this other than to get sign extension?

dalecki> 3. Fix the virt_to_phys mapping for scatter-gather transfers
dalecki> as well as some other minor tidups here and there.

What are you trying to achieve there? You run virt_to_phys() on a user
space address as far as I can read and stick it into something
labelled xferaddr? Normally you should never need the physical address
in a device driver unless you want to play with page table settings or
the like. If the address is to be handed to a DMA engine you should
never take the physical address, but rather use virt_to_bus() or even
better use the new 2.3+ PCI DMA API (pci_map_single()).

Jes
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      parent reply	other threads:[~2000-11-19 21:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-18 23:00 [PATCH] megaraid driver update for 2.4.0-test10 dalecki
2000-11-18 22:27 ` Jeff Garzik
2000-11-19 17:02   ` dalecki
2000-11-19  1:50 ` Miquel van Smoorenburg
2000-11-19 17:06   ` dalecki
2000-11-19 21:28 ` Jes Sorensen [this message]

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=d3zoivtzw3.fsf@lxplus015.cern.ch \
    --to=jes@linuxcare.com \
    --cc=dalecki@evision-ventures.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.