From: Alex deVries <adevries@thepuffingroup.com>
To: Grant Grundler <grundler@cup.hp.com>
Cc: parisc-linux@thepuffingroup.com, grundler@milano.cup.hp.com
Subject: Re: [parisc-linux] Dino developments...
Date: Mon, 04 Oct 1999 12:05:44 -0400 [thread overview]
Message-ID: <37F8D058.3B46449E@thepuffingroup.com> (raw)
In-Reply-To: 199910040445.VAA15000@milano.cup.hp.com
Grant Grundler wrote:
> Alex deVries wrote:
> > I've fixed up a couple of things in the kernel:
> > - PCI bus walking happens in the *right place*, pci_init().
>
> Ok. Were you able to salvage what I had submitted then?
> I was under the impression pci_init() wouldn't work. Registration of
> the pci_bus_ops for each Dino looked like a problem.
Yeah, I definitely re-used a lot of existing work. I got pci_init() to
work properly.
> Oh. I think I got it. Each dino registers pci_bus_ops when it's
> "discovered" and pci_init() is called later...is that right?
Yeah, although if I understand the kernel code properly, the first PCI
bus scan is done from within pci_init(). All the others are called when
the others are detected. Right now the dino_init() call is in the wrong
place.
> I'll start reviewing card-mode Dino initialization and see what we can
> do for MMIO. I have to understand more about what the "right" thing for
> linux is WRT I/O address management. This has to take place sometime
> between when card-mode Dino is "discovered" and when PCI bus walk completes.
> (So we know how much space is needed.)
Can we gather a memory IO map based on what we find in the inventory
code with the mem_map() PDC calls?
> What about interrupts?
> Is alloc_irq() handing virtual IRQ's back to the PCI drivers for the
> respective dino irq_region?
> I'm curios if/how it is supposed to work and might take a peek at this
> as well. Once this works, the box should be able to send mail - that's
> a key milestone for HP folks..
I really havent' looked at interrupts at all yet in PCI, so please, have
a look at it.
About sending mail: that'd require actually running a userland program
(unless you want to embed something like elm or emacs into the kernel),
and I'm not sure how close we are to that.
- Alex
--
Alex deVries
Vice President of Engineering
The Puffin Group
next prev parent reply other threads:[~1999-10-04 15:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-03 23:29 [parisc-linux] Dino developments Alex deVries
1999-10-04 4:45 ` Grant Grundler
1999-10-04 16:05 ` Alex deVries [this message]
1999-10-04 5:30 ` Grant Grundler
1999-10-04 19:57 ` Alex deVries
-- strict thread matches above, loose matches on Subject: below --
1999-10-07 21:00 Grant Grundler
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=37F8D058.3B46449E@thepuffingroup.com \
--to=adevries@thepuffingroup.com \
--cc=grundler@cup.hp.com \
--cc=grundler@milano.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