From: Philipp Rumpf <prumpf@suse.de>
To: Grant Grundler <grundler@cup.hp.com>, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux-cvs] grundler
Date: Thu, 2 Sep 1999 11:08:31 +0200 [thread overview]
Message-ID: <19990902110831.I629@suse.de> (raw)
In-Reply-To: <199909012302.RAA04044@puffin.external.hp.com>; from grundler@puffin.external.hp.com on Wed, Sep 01, 1999 at 05:02:23PM -0600
On Wed, Sep 01, 1999 at 05:02:23PM -0600, grundler@puffin.external.hp.com wrote:
> Update of /home/cvs/parisc/linux/drivers/gecko
> In directory puffin.external.hp.com:/tmp/cvs-serv4014/linux/drivers/gecko
>
> Modified Files:
> dino.c
okay, let's go through the changes here too:
- strange STATIC define with a comment about "performance" kernels.
I don't see the point. Is there one ?
- use of irq_t all over the place
I don't mind this, but it really doesn't matter and just using int has the
advantage of still being able to printk it.
- Dino-specific IRQ management
As far as I am concerned, there is no way I want to have 5 different IRQ
managements in the kernel. It is not needed, the performance loss is minimal,
I don't see any other advantages to it. (I just skipped that code so you don't
get all my complaints)
- #if 0-ing out dino_walk_bus
remove it. we really don't need any #if 0 bodies swimming around our trees.
- check for potentially defect Dino chips
Nothing negative I can say about that
- +** TODO: Dino needs a method to look at and possibly "claim" GSC devices.
it's what you #if 0-ed out. (
struct gsc_dev *dev = gsc_devices;
while(dev = dev->next) {
if(is_dino(dev)) {
blah blah
}
}
).
- split dino init into two parts
I don't see the point.
- changes to dino_config_write_byte aso (renaming them in the process)
Is this for supporting more than one PCI bus via pci-to-pci bridges ?
looks unnecessary to me, but I really don't know
- +** Performance is going to stink if drivers use I/O port instead
+** of MMIO.
This is not Dino-specific.
- use of readb aso instead of gsc_readb aso
gsc_readb is there for a reason.
Philipp Rumpf
next parent reply other threads:[~1999-09-02 9:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199909012302.RAA04044@puffin.external.hp.com>
1999-09-02 9:08 ` Philipp Rumpf [this message]
1999-09-02 14:43 ` [parisc-linux-cvs] grundler Matthew Wilcox
[not found] <199909012302.RAA04026@puffin.external.hp.com>
1999-09-02 9:12 ` Philipp Rumpf
1999-09-02 17:20 ` Grant Grundler
1999-09-03 11:15 ` Philipp Rumpf
1999-09-03 16:22 ` Alex deVries
[not found] <199909012302.RAA04035@puffin.external.hp.com>
1999-09-02 8:40 ` Philipp Rumpf
1999-09-02 14:26 ` Philipp Rumpf
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=19990902110831.I629@suse.de \
--to=prumpf@suse.de \
--cc=grundler@cup.hp.com \
--cc=parisc-linux@thepuffingroup.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