From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
Subject: Re: Modpost warning on Alchemy
Date: Thu, 02 Aug 2007 16:49:59 +0400 [thread overview]
Message-ID: <46B1D2F7.8000002@ru.mvista.com> (raw)
In-Reply-To: <Pine.LNX.4.64N.0708020945020.22591@blysk.ds.pg.gda.pl>
Hello.
Maciej W. Rozycki wrote:
>>>So what is the issue with the size then? How big is the area?
>> I've already said: 4 gigs! At least in theory, actually it's 2 gigs due to
> Oh, I mistook it for the base physical address, sorry.
That's 24 gigs. :-)
>>a device # being limited to 0 thru 19 (address bits 11 thru 30 are used as
>>IDSELx).
> It does not help too much with a 32-bit virtual address space indeed.
> Though I gather it has to be very sparsely populated as 16MiB is enough to
> cover the whole configuration space of a single PCI bus tree. Thus it has
Hm, maybe 16 MiB would be enough indeed, as the Alchemy CPUs are known to
not support bus masters behind PCI bridges...
> to be another example where the chip designer "forgot" to talk to software
> people. Or a shifter was traded for software performance and complexity.
> ;-)
I certainly agree here. :-)
>> There was no need to tell me about how KSEG0/1/2 work -- that's why I
>>cosidered it wasting time. :-)
> As I say -- the key is how you look at it. There are other readers on
> the list who may benefit; it is archived too. In this sense I can hardly
> consider it a waste of time. And it was fun to explain and no fun shall
> be ever considered of no use. :-)
Depends on the source of fun. :-)
> Maciej
WBR, Sergei
next prev parent reply other threads:[~2007-08-02 12:48 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 11:52 Modpost warning on Alchemy Ralf Baechle
2007-08-01 12:23 ` Sergei Shtylyov
2007-08-01 12:53 ` Maciej W. Rozycki
2007-08-01 13:13 ` Sergei Shtylyov
2007-08-01 13:18 ` Sergei Shtylyov
2007-08-01 15:38 ` Maciej W. Rozycki
2007-08-01 15:44 ` Sergei Shtylyov
2007-08-01 16:26 ` Maciej W. Rozycki
2007-08-01 16:37 ` Sergei Shtylyov
2007-08-01 16:54 ` Maciej W. Rozycki
2007-08-01 17:06 ` Sergei Shtylyov
2007-08-02 9:14 ` Maciej W. Rozycki
2007-08-02 12:49 ` Sergei Shtylyov [this message]
2007-08-02 13:27 ` Maciej W. Rozycki
2007-08-02 14:15 ` Sergei Shtylyov
2007-08-02 14:33 ` Maciej W. Rozycki
2007-08-01 17:10 ` Alan Cox
2007-08-02 9:24 ` Maciej W. Rozycki
2007-08-01 17:09 ` Sergei Shtylyov
2007-08-02 9:39 ` Maciej W. Rozycki
2007-08-02 10:15 ` Ralf Baechle
2007-08-02 10:17 ` Maciej W. Rozycki
2007-08-02 12:53 ` Sergei Shtylyov
2007-08-02 13:00 ` Sergei Shtylyov
2007-08-02 13:35 ` Maciej W. Rozycki
2007-08-02 14:10 ` Sergei Shtylyov
2007-08-02 14:21 ` Maciej W. Rozycki
2007-08-01 15:39 ` Alan Cox
2007-08-01 15:49 ` Maciej W. Rozycki
2007-08-01 15:58 ` Alan Cox
2007-08-01 16:00 ` Maciej W. Rozycki
2007-08-01 16:21 ` Ralf Baechle
2007-08-01 16:33 ` Maciej W. Rozycki
2007-08-02 9:25 ` Ralf Baechle
2007-08-02 9:44 ` Maciej W. Rozycki
2007-08-01 16:01 ` Sergei Shtylyov
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=46B1D2F7.8000002@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=ralf@linux-mips.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