From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
Cc: root@chaos.analogic.com, Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: linux-2.4.0-test9
Date: Sat, 04 Nov 2000 03:26:30 -0500 [thread overview]
Message-ID: <3A03C836.3A813A2A@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1001103213717.2705A-100000@chaos.analogic.com> <3A037E9F.55B16633@mandrakesoft.com> <20001104092049.W7204@nightmaster.csn.tu-chemnitz.de>
Ingo Oeser wrote:
>
> On Fri, Nov 03, 2000 at 10:12:31PM -0500, Jeff Garzik wrote:
> > But if you are going to eliminate info->vxi_base, it seems like that
> > would flush out all direct de-refs, whether they are buried in an
> > obscure macro or not. And if you find all that crap, you might as well
> > use readb/writel at that point...
> >
> > info->registers[0x7FF] = newvalue;
> > becomes
> > writel(newvalue, &info->registers[0x7FF]);
> > and
> > regval = info->registers[0x7FF];
> > becomes
> > regval = readl(&info->registers[0x7FF]);
>
> Wasn't this the clean and recommended interface anyway?
> (ref. IO-mapping.txt:150)
Absolutely! We are talking about an old driver, though, and due
consideration has to be given to not breaking existing code :)
Jeff
--
Jeff Garzik | Dinner is ready when
Building 1024 | the smoke alarm goes off.
MandrakeSoft | -/usr/games/fortune
-
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/
next prev parent reply other threads:[~2000-11-04 8:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-03 22:54 linux-2.4.0-test9 Richard B. Johnson
2000-11-04 1:05 ` linux-2.4.0-test9 Jeff Garzik
2000-11-04 2:49 ` linux-2.4.0-test9 Richard B. Johnson
2000-11-04 3:12 ` linux-2.4.0-test9 Jeff Garzik
2000-11-04 8:20 ` linux-2.4.0-test9 Ingo Oeser
2000-11-04 8:26 ` Jeff Garzik [this message]
2000-11-04 10:55 ` linux-2.4.0-test9 Keith Owens
2000-11-06 14:45 ` linux-2.4.0-test9 Richard B. Johnson
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=3A03C836.3A813A2A@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=ingo.oeser@informatik.tu-chemnitz.de \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.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 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.