All of lore.kernel.org
 help / color / mirror / Atom feed
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 18:15:50 +0400	[thread overview]
Message-ID: <46B1E716.6070807@ru.mvista.com> (raw)
In-Reply-To: <Pine.LNX.4.64N.0708021349040.22591@blysk.ds.pg.gda.pl>

Maciej W. Rozycki wrote:

>>>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...

>  That is unrelated -- for configuration accesses (assuming the basic 

    I mean who needs crippled subordinate busses? ;-)

> configuration space) you need: 8 bits for the bus number + 5 bits for the 
> device number + 3 bits for the function number + 8 bits for the register 
> number.  The total is 24 bits.

    Yeah, that the format of type 1 cycles.

>  It is up to hardware to sort it out and put the right bits on the bus.

    Unfortunately, Alchemy designers were too lazy to implement a simple 
translation scheme for type 0 cycles. They probably though that with 36-bit 
bus the may not limit themselves... :-)

>   Maciej

WBR, Sergei

  reply	other threads:[~2007-08-02 14:13 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
2007-08-02 13:27                         ` Maciej W. Rozycki
2007-08-02 14:15                           ` Sergei Shtylyov [this message]
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=46B1E716.6070807@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.