From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Geoff Levand <geoffrey.levand@am.sony.com>, linux-serial@vger.kernel.org
Subject: Re: pmac serial_pci_guess_board problem
Date: Sat, 05 Nov 2005 09:53:19 +1100 [thread overview]
Message-ID: <1131144799.29195.31.camel@gaston> (raw)
In-Reply-To: <20051104225051.GC12026@flint.arm.linux.org.uk>
> That's the expected size of the ports. Remember this is a heuristic
> for finding the correct details of the ports. Some cards seem to
> have regions of 16 bytes which aren't serial ports.
>
> I'm _very_ nervous about changing this, especially as it pre-dates
> my time and you seem to imply that it's an OF problem. Can't it be
> fixed up in a PCI quirk?
Could be yes. a ppc64 specific one that re-do the BAR sizing... I wonder
what's up with OF tho ... Maybe Apple's OF can't assign BARs smaller
than 16 bytes ?
Ben.
prev parent reply other threads:[~2005-11-04 22:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 21:27 pmac serial_pci_guess_board problem Geoff Levand
2005-11-04 21:47 ` Benjamin Herrenschmidt
2005-11-04 22:50 ` Russell King
2005-11-04 22:53 ` Benjamin Herrenschmidt [this message]
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=1131144799.29195.31.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=geoffrey.levand@am.sony.com \
--cc=linux-serial@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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