From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Sven Luther <sven.luther@wanadoo.fr>
Cc: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>,
Rob Baxter <robb@synergymicro.com>
Subject: Re: multiple separate pci bridges ...
Date: Tue, 06 Jan 2004 08:28:15 +1100 [thread overview]
Message-ID: <1073338095.9497.70.camel@gaston> (raw)
In-Reply-To: <20040105164038.GA16158@iliana>
> Ok, i got it to work finally, at least upto asking me for a root
> filesystem, which i don't yet have on this harddisk.
>
> Now, I have some technical questions about how to best do a few things.
>
> I was recommended to set the ppc_md.pci_exclude_device so that the
> device 0 (the marvell bridge itself) is not seen by linux. I did this by
> following the 4xx example, which should be ok.
Actually, just hiding the BARs with a quirk should be enough (what
I do for the CPC710)...
> But, i have to do access some address which i need to ioremap. I created
> a hose->cfg_peg2_magic to to put this ioremapped address in. I guess
> this is not the most clean way of doing this or something, any hint on
> how to best do it ? I need to set this in chrp_find_bridges or something
> such, and use the address in the read/write_config functions.
What for ? you can eventually ioremap some lower address in
host->cfg_addr or cfg_data and then use offsets from these addresses,
though it's not recommended to ioremap too large spaces. You can also
just ioremap that in a global once... I do that for a few things in
pmac_feature.c, like the northbridge registers.
> Also, i had to manually set hose->bus_offset = 0x10, since that didn't
> seem to be set automatically. I don't know why though.
Why do you need hose->bus_offset ? For indirect_pci ? Well... that's
a kludge, you should rather fix indirect_pci to use first_busno
instead... I don't know where this bus_offset comes from in the first
place, it's defined in pci_controller but not used at all in 2.6...
(BTW. You should really work on 2.6, not 2.4...)
> And finally, about the stuff which blocked me most, i am somewhat
> bewildered. I use this :
>
> data = 0x80000000 | ((dev->bus->number - hose->bus_offset) << 16)
> | (dev->devfn << 8) | (offset & 0xff);
>
> As the address to write to, but the indirect pci stuff uses offset &
> 0xfc, which blanks bits 0 & 1 for pci config type selection. What am i
> misunderstanding or doing wrong here ?
Normally, you write the offset 32 bits aligned, and then you add those
2 missing bits to the cycle used to actually read the config space
(access to the data register).
But then... read your bridge spec.
> A, and a last question to Rob Baxter, did you manage to get the builtin
> gigabyte ethernet port to work, and if yes, with which code, an
gigabit you mean ? :) gigabyte would be nice though...
> existing driver or some home built driver. Can you eventually share the
> code or something such ?
What cell is it ?
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-01-05 21:28 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-01 18:11 multiple separate pci bridges Sven Luther
2004-01-02 4:03 ` Benjamin Herrenschmidt
2004-01-02 7:40 ` Sven Luther
2004-01-02 7:49 ` Benjamin Herrenschmidt
2004-01-04 21:03 ` Sven Luther
2004-01-04 21:45 ` Benjamin Herrenschmidt
2004-01-04 22:06 ` Sven Luther
2004-01-05 16:40 ` Sven Luther
2004-01-05 21:28 ` Benjamin Herrenschmidt [this message]
2004-01-05 21:42 ` Sven Luther
2004-01-05 22:12 ` Benjamin Herrenschmidt
2004-01-06 7:39 ` Sven Luther
2004-01-06 8:00 ` Benjamin Herrenschmidt
2004-01-06 8:11 ` Sven Luther
2004-01-06 14:40 ` Geert Uytterhoeven
2004-01-06 14:45 ` Sven Luther
2004-01-06 15:33 ` Rob Baxter
2004-01-06 17:44 ` Sven Luther
2004-01-06 21:37 ` Benjamin Herrenschmidt
2004-01-06 22:10 ` Marcus Barrow
2004-01-06 22:17 ` Rob Baxter
2004-01-06 22:31 ` Benjamin Herrenschmidt
2004-01-07 2:35 ` Sven Luther
2004-01-07 2:36 ` Benjamin Herrenschmidt
2004-01-07 2:40 ` Sven Luther
2004-01-07 9:02 ` Michael Schmitz
2004-01-07 9:23 ` Benjamin Herrenschmidt
2004-01-07 9:56 ` Sven Luther
2004-01-07 10:27 ` Michael Schmitz
2004-01-13 9:56 ` Sven Luther
2004-01-13 10:26 ` Sven Luther
2004-01-18 12:15 ` Sven Luther
2004-01-18 13:00 ` Michel Dänzer
2004-01-18 13:14 ` Sven Luther
2004-01-19 9:12 ` Benjamin Herrenschmidt
2004-01-18 22:27 ` Sven Luther
2004-01-18 22:59 ` Benjamin Herrenschmidt
2004-01-19 9:21 ` Sven Luther
2004-01-18 23:24 ` Benjamin Herrenschmidt
2004-01-05 21:38 ` Marcus Barrow
2004-01-06 7:14 ` Sven Luther
2004-01-06 7:56 ` Benjamin Herrenschmidt
2004-01-06 8:20 ` Sven Luther
2004-01-02 18:34 ` Geert Uytterhoeven
2004-01-02 15:18 ` Rob Baxter
2004-01-02 23:56 ` Benjamin Herrenschmidt
2004-01-03 0:27 ` Rob Baxter
2004-01-03 1:12 ` Benjamin Herrenschmidt
2004-01-05 0:52 ` Rob Baxter
2004-01-05 2:13 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2004-01-06 20:53 Marcus Barrow
2004-01-06 21:09 Marcus Barrow
2004-01-06 22:59 ` Benjamin Herrenschmidt
2004-01-06 23:00 ` Benjamin Herrenschmidt
2004-01-18 14:44 Sven Luther
2004-01-18 16:33 ` Michel Dänzer
2004-01-18 17:28 ` Sven Luther
2004-01-18 18:24 ` Michel Dänzer
2004-01-18 22:20 ` Sven Luther
2004-01-18 23:33 ` Michel Dänzer
2004-01-19 9:55 ` Sven Luther
2004-01-19 13:48 ` Sven Luther
2004-01-19 13:54 ` Geert Uytterhoeven
2004-01-19 14:00 ` Sven Luther
2004-01-19 14:02 ` Michel Dänzer
2004-01-19 14:16 ` Sven Luther
2004-01-19 14:31 ` Michel Dänzer
2004-01-19 9:11 ` Benjamin Herrenschmidt
2004-01-18 22:33 ` Sven Luther
2004-01-18 23:23 ` Michel Dänzer
2004-01-18 23:42 ` Benjamin Herrenschmidt
2004-01-19 0:03 ` Michel Dänzer
2004-01-19 10:08 ` Geert Uytterhoeven
2004-01-19 11:41 ` Benjamin Herrenschmidt
2004-01-19 12:03 ` Sven Luther
2004-01-19 21:35 ` Benjamin Herrenschmidt
2004-01-19 22:08 ` Sven Luther
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=1073338095.9497.70.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=robb@synergymicro.com \
--cc=sven.luther@wanadoo.fr \
/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;
as well as URLs for NNTP newsgroup(s).