From: Jeremy Higdon <jeremy@SGI.COM>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Aniket Malatpure <aniket@SGI.COM>,
akmp@osdl.org, gwh@SGI.COM, jbarnes@SGI.COM,
aniket_m@hotmail.com, linux-kernel@vger.kernel.org
Subject: Re: Patch to add support for SGI's IOC4 chipset
Date: Tue, 7 Oct 2003 01:27:27 -0700 [thread overview]
Message-ID: <20031007082727.GA27934@sgi.com> (raw)
In-Reply-To: <200310041930.15385.bzolnier@elka.pw.edu.pl>
Hello Bartlomiej,
I have a few questions. I'm going to be submitting the rest
of the patches that Aniket was working on, as he started at a new
company today (he was attempting to finish the submission before he
left). Please forgive a lack of expertise on my part.
On Sat, Oct 04, 2003 at 07:30:15PM +0200, Bartlomiej Zolnierkiewicz wrote:
>
> > + return p - buffer;
> > +}
> >
> > >Do you really need /proc/ide/sgiioc4?
> > >You can print revision number during init.
> >
> > It has been helpful to be able to see the firmware revision num anytime
> > during system operation.
> > So the new patch still creates the above entry.
>
> I don't buy this, lspci can be used :-).
lspci gives the version number.
/proc/ide/sgiioc4 gives you:
SGI IOC4 Chipset rev 79.
Chipset has 1 IDE channel and supports 2 devices on that channel.
Chipset supports DMA in MultiMode-2 data transfer protocol.
Is the # of IDE channels/devices and the DMA mode also available elsewhere?
> > + int ddir);
> > +static unsigned int __init pci_init_sgiioc4(struct pci_dev
> > *dev,ide_pci_device_t *d);
> >
> > >Most of this declarations are not needed as sgiioc4.h is only included
> > > from shiioc4.c.
> >
> > The sgiioc4.h file has been removed in the new patch.
>
> sgiioc4.h was removed, but declarations weren't.
> You can shuffle code around to get rid of them.
How important is this to you? It seems more a style issue. I agree with
you, by the way. When I write code, I try to minimize forward declarations.
If I can get rid of some easily, will that be good enough?
> There are no .enablebits on SGI IOC4? Please add a comment about it.
What are they used for (i.e. what are you looking for in the comment)?
> sgiioc4_init_one():
> + pci_read_config_dword(dev, PCI_CLASS_REVISION, &class_rev);
> + class_rev &= 0xff;
>
> Access to PCI devices before pci_enable_device()
> (it is called later in pci_init_sgiioc4).
Is pci_enable_device required before a config space access?
I will make changes in accordance with the other comments and based on
your responses to this.
Thanks
jeremy
next prev parent reply other threads:[~2003-10-07 8:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-02 23:28 Aniket Malatpure
2003-10-03 0:43 ` Andrew Morton
2003-10-03 14:45 ` Bartlomiej Zolnierkiewicz
2003-10-03 14:55 ` Jeff Garzik
2003-10-03 15:13 ` Bartlomiej Zolnierkiewicz
2003-10-04 1:52 ` Aniket Malatpure
2003-10-04 0:32 ` Aniket Malatpure
2003-10-04 17:30 ` Bartlomiej Zolnierkiewicz
2003-10-07 8:27 ` Jeremy Higdon [this message]
2003-10-07 13:27 ` Bartlomiej Zolnierkiewicz
2003-10-08 3:38 ` Jeremy Higdon
2003-10-16 18:20 ` Bartlomiej Zolnierkiewicz
2003-10-21 6:35 ` Jeremy Higdon
2003-10-21 14:39 ` Bartlomiej Zolnierkiewicz
2003-10-22 4:30 ` Jeremy Higdon
2003-10-22 18:31 ` Bartlomiej Zolnierkiewicz
2003-10-23 4:34 ` Jeremy Higdon
2003-10-25 2:09 ` Jeremy Higdon
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=20031007082727.GA27934@sgi.com \
--to=jeremy@sgi.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=akmp@osdl.org \
--cc=aniket@SGI.COM \
--cc=aniket_m@hotmail.com \
--cc=gwh@SGI.COM \
--cc=jbarnes@SGI.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome