On Tue, 02 Oct 2007 16:10:53 -0700
Badari Pulavarty [EMAIL PROTECTED] wrote:
Otherwise, we need to add arch-specific hooks in hotplug-remove
code to be able to do this.
Isn't it just a matter of abstracting the test for a valid range of
memory? If it's really hard to abstract that,
Olof Johansson writes:
This makes the kernel use 1TB segments for all kernel mappings and for
user addresses of 1TB and above, on machines which support them
(currently POWER5+ and POWER6).
PA6T supports them as well :)
In the patch, we don't actually hard-code the CPU_FTR_1T_SEGMENT
Joachim Fenkes writes:
Replace struct ibmebus_dev and struct ibmebus_driver with struct of_device
and struct of_platform_driver, respectively. Match the external ibmebus
interface and drivers using it.
Signed-off-by: Joachim Fenkes [EMAIL PROTECTED]
---
Will Schmidt writes:
I still need to test this code for performance issues, and this version
could still use some cosmetic touchups, so I dont think we want this to
go into a tree yet. I am reposting this primarily to indicate the prior
version isnt quite right, and so Jon can rebase to this
On Wed, Oct 03, 2007 at 01:07:58PM +1000, Paul Mackerras wrote:
Olof Johansson writes:
This makes the kernel use 1TB segments for all kernel mappings and for
user addresses of 1TB and above, on machines which support them
(currently POWER5+ and POWER6).
PA6T supports them as well
On Wed, 2007-10-03 at 11:19 +1000, Tony Breeds wrote:
On Wed, Oct 03, 2007 at 10:30:16AM +1000, Michael Ellerman wrote:
I realise it'll make the patch bigger, but this doesn't seem like a
particularly good name for the variable anymore.
Sure, what about?
Better .. but .. :D
diff
On 10/2/07, Benjamin Herrenschmidt [EMAIL PROTECTED] wrote:
My opinion is that since it is driver-specific code anyway, then it
belongs with the driver. Plus a driver writer for ARM doesn't need to
write them. It's the powerpc or microblaze developer who will do it.
If the driver
On Tue, 2007-10-02 at 22:18 -0600, Grant Likely wrote:
For many drivers, I think that is already the case. USB OHCI is a
prime example where there are both PCI and platform_bus bindings among
others. It seems to me that the bus binding effectively translates
down to where do I go to get
On Wed, 3 Oct 2007, Paul Mackerras wrote:
Tony Breeds writes:
@@ -982,6 +906,10 @@ void __init time_init(void)
write_sequnlock_irqrestore(xtime_lock, flags);
+ /* Register the clocksource, if we're not running on iSeries */
+ if
Discussions with firmware architects have confirmed that the bit in
the ibm,pa-features property that indicates support for
cache-inhibited large (= 64kB) page mappings does in fact mean that
the hypervisor allows 64kB mappings to I/O devices.
Thus we can now enable the code that tests that bit
There was a query a while back about whether lmb_remove_region() was
correct to unconditionally decrement rgn-cnt:
http://ozlabs.org/pipermail/linuxppc-dev/2007-March/033261.html
AFAICT there is no bug at the moment because the two callers ensure that
they only pass a value of r which is
On Fri, Sep 28, 2007 at 10:16:51AM -0500, Milton Miller wrote:
[snip]
Actually, there is another approach: put this converter in kexec's
purgatory or even the kexec program. It can then run conditionally
under command line flags to keep compatibility with the old kernels.
If and when
On Fri, Sep 28, 2007 at 06:23:09PM +0400, Valentine Barshak wrote:
David Gibson wrote:
On Mon, Sep 24, 2007 at 03:36:27PM +0400, Valentine Barshak wrote:
Currently zImage is linked at the 4MB base address.
Some platforms (using cuboot, treeboot) need the zImage's
entry point and base
This patch makes a number of Makefile cleanups and improvements:
- We use more generic rules to invoke flex and bison, which is
useful for some of the other changes.
- We use the name dtc-lexer.lex.c for the flex output, instead
of the default lex.yy.c. That means less potential
101 - 114 of 114 matches
Mail list logo
