2008/10/15 Simon Horman <[EMAIL PROTECTED]>
> On Tue, Oct 14, 2008 at 07:11:19PM +0400, Maxim Uvarov wrote:
> > Hello all,
> >
> > As you all know it is not easy to count exact value of memory ranges from
> > device tree on powerpc.
> > It very depends on how dts file was written. What do you thin
* Adrian Bunk <[EMAIL PROTECTED]> [2008-10-14 20:58:22]:
> On Tue, Oct 14, 2008 at 09:10:33AM -0700, Brandeburg, Jesse wrote:
> > Brice Goglin wrote:
> > > Adrian Bunk wrote:
> > >> But considering that igb is in a similar situation it would be nice
> > >> if all 3 drivers would handle it the same
This patch implements the memory notifier to update the busmap instantly
instead of rebuilding the whole map. This is necessary because
walk_memory_resource provides different information than required during memory
hotplug.
Signed-off-by: Hannes Hering <[EMAIL PROTECTED]>
---
This patch is based
> > Well, at the time of the sample, the other CPU indeed -seems- to be in
> > an IRQ disabled section yes.
>
> This is not really a sample. The hardirqs enable/disable is actually tracked
> using the TRACE_{EN,DIS}ABLE_INTS macros.
That's what I meant. IE. the hardirq state was updated by the
What about the mb86290 framebuffer driver directly from Fujitsu which is
in the mainline kernel?
It's from 2003 and supports only until 86293, but can it be used as a
basis for a proper fb driver? It has a lot of features indeed...
M
Anatolij Gustschin ha scritto:
This patch adds framebuffer
The patch allows to specify that an SPI device needs an active high chip
select.
Signed-off-by: Wolfgang Ocker <[EMAIL PROTECTED]>
---
--- linux-2.6.27-rc7/drivers/of/of_spi.c.of_spi_cshigh 2008-09-22
00:29:55.0 +0200
+++ linux-2.6.27-rc7/drivers/of/of_spi.c2008-09-29 13:43:06.0
Matteo Fortini wrote:
> What about the mb86290 framebuffer driver directly from Fujitsu which is
> in the mainline kernel?
This mb86290 framebuffer driver from Fujitsu isn't in mainline, it
is in the DENX Linux Kernel tree.
> It's from 2003 and supports only until 86293, but can it be used as a
On Wed, Oct 15, 2008 at 03:00:47PM +0200, Wolfgang Ocker wrote:
> The patch allows to specify that an SPI device needs an active high chip
> select.
This look reasonable to me. Anyone else have comments on this binding?
g.
>
> Signed-off-by: Wolfgang Ocker <[EMAIL PROTECTED]>
> ---
>
> --- li
Ok I understand.
FWIW, based on my trials:
* DirectFB support on BE hosts is somehow easier than with
carminefb: the patches from Nikita Egorov are working almost out
of the box (they basically change every single access to memory so
that it becomes ABGR, so that a simple memcp
On Tue, Oct 14, 2008 at 03:33:46PM +0200, Wolfram Sang wrote:
> What about these? :)
>
> http://oldpatchwork.ozlabs.org/linuxppc-embedded/patch?id=20188
> (remove obsolete code from mpc52xx_phy)
I'm not going to pick this one up yet (as mentioned in my earlier
email)
> http://oldpatchwork.ozlabs
On Wed, 15 Oct 2008, Benjamin Herrenschmidt wrote:
> On Wed, 2008-10-15 at 13:46 +0200, Geert Uytterhoeven wrote:
> > On Wed, 15 Oct 2008, Benjamin Herrenschmidt wrote:
> > > > > Well, at the time of the sample, the other CPU indeed -seems- to be in
> > > > > an IRQ disabled section yes.
> > > >
On Wed, 2008-10-15 at 11:25 +0200, Geert Uytterhoeven wrote:
> On Wed, 15 Oct 2008, Benjamin Herrenschmidt wrote:
> > On Tue, 2008-10-14 at 11:32 +0200, Geert Uytterhoeven wrote:
> > > which points again to smp_call_function_single...
> >
> > Yup, it doesn't bring more information. At this stage,
* Kumar Gala | 2008-10-15 08:25:54 [-0500]:
>
> On Oct 15, 2008, at 3:59 AM, Sebastian Andrzej Siewior wrote:
>
>> * Sebastian Andrzej Siewior | 2008-10-15 00:49:46 [+0200]:
>>
is the -mabi=no-spe really needed?
>>> It seems to work the other way around (without -mabi=no-spe but with
>>> -mab
Benjamin Herrenschmidt wrote:
On Tue, 2008-10-14 at 03:52 -0700, Kevin Diggs wrote:
Kevin Diggs wrote:
Hi,
I managed to wrestle my gigE to the ground and get it to boot
2.6.27. I have, however, noticed that some messages are showing up in
dmesg. There are alot of them. They are continuous
On Wed, 15 Oct 2008, Kevin Diggs wrote:
> I cut a deal with my 8600 to get it to boot 2.6.27. It does not seem
> to work right either.
>
> The error message that shows up in dmesg is (the messages that show
> up for the gigE appear to be for two different busses (hubs?):
>
> hub 1-0:1.0: state 7
On Wed, Oct 15, 2008 at 08:22:28AM -0600, Grant Likely wrote:
> On Wed, Oct 15, 2008 at 03:00:47PM +0200, Wolfgang Ocker wrote:
> > The patch allows to specify that an SPI device needs an active high chip
> > select.
>
> This look reasonable to me. Anyone else have comments on this binding?
Look
I am using the stock canyonlands 460EX development board. I have
the 4L (port 1) configured as a root-complex. I also have a SIL
pci-e sata card. When I plug the sata card directly into the
canyonlands, everything works as expected. The sil is detected
in Linux and I can read/write the disk.
On Oct 15, 2008, at 9:43 AM, Sebastian Andrzej Siewior wrote:
* Kumar Gala | 2008-10-15 08:25:54 [-0500]:
On Oct 15, 2008, at 3:59 AM, Sebastian Andrzej Siewior wrote:
* Sebastian Andrzej Siewior | 2008-10-15 00:49:46 [+0200]:
is the -mabi=no-spe really needed?
It seems to work the other
On Wed, 2008-10-15 at 10:41 +0200, Arnd Bergmann wrote:
> On Wednesday 15 October 2008, Robert Richter wrote:
> > there are still these OProfile patches for powerpc pending:
> >
> > Carl Love (1):
> > powerpc/cell/oprofile: fix mutex locking for spu-oprofile
> >
> > Roel Kluin (1):
> >
On Wed, 15 Oct 2008, Benjamin Herrenschmidt wrote:
> On Tue, 2008-10-14 at 11:32 +0200, Geert Uytterhoeven wrote:
> > which points again to smp_call_function_single...
>
> Yup, it doesn't bring more information. At this stage, your 'other' CPU
> is stuck with interrupts disabled. Hard to tell what
* Sebastian Andrzej Siewior | 2008-10-15 00:49:46 [+0200]:
>>is the -mabi=no-spe really needed?
>It seems to work the other way around (without -mabi=no-spe but with
>-mabi=no-spe) alteast I did not find anything in do_syslog() or while
>browsing through the dissasm. I do a boot check tomorrow.
O
On Oct 15, 2008, at 3:59 AM, Sebastian Andrzej Siewior wrote:
* Sebastian Andrzej Siewior | 2008-10-15 00:49:46 [+0200]:
is the -mabi=no-spe really needed?
It seems to work the other way around (without -mabi=no-spe but with
-mabi=no-spe) alteast I did not find anything in do_syslog() or whi
On Wed, 15 Oct 2008, Benjamin Herrenschmidt wrote:
> > > Well, at the time of the sample, the other CPU indeed -seems- to be in
> > > an IRQ disabled section yes.
> >
> > This is not really a sample. The hardirqs enable/disable is actually tracked
> > using the TRACE_{EN,DIS}ABLE_INTS macros.
>
Patch corrected. ( git_kexec_powerpc_v2.patch is attached.)
I tested it on ppc64 pasemi electra board. Both kexec -l and kexec -p works.
Maxim.
2008/10/15 Simon Horman <[EMAIL PROTECTED]>
> On Tue, Oct 14, 2008 at 07:11:19PM +0400, Maxim Uvarov wrote:
> > Hello all,
> >
> > As you all know it
On Monday, October 13, 2008 5:55 pm Benjamin Herrenschmidt wrote:
> This patch adds support for legacy_io and legacy_mem files in
> bus class directories in sysfs for powerpc
>
> Signed-off-by: Benjamin Herrenschmidt <[EMAIL PROTECTED]>
Ok, applied this one. Should be pushing to Linus soon.
Than
On Wed, 15 Oct 2008, Benjamin Herrenschmidt wrote:
> On Wed, 2008-10-15 at 11:25 +0200, Geert Uytterhoeven wrote:
> > On Wed, 15 Oct 2008, Benjamin Herrenschmidt wrote:
> > > On Tue, 2008-10-14 at 11:32 +0200, Geert Uytterhoeven wrote:
> > > > which points again to smp_call_function_single...
> > >
Most of the platforms were printing the size of the memory
in their show_cpuinfo implementations. This moves that to
the common show_cpuinfo, so that all 32-bit platforms will
now print the size of memory. I also update the code
to deal with the fact that total_memory is now a phys_addr_t.
Signed
Greetings, all!
I just posted code to implement a Generic PWM Device API to linux-embedded. If
you need them, archives of that mailing list are available at the following link
(and elsewhere):
http://www.mail-archive.com/[EMAIL PROTECTED]/
Previous versions of this code were posted on linux-ar
>From aa5810fa545515c9f383e3e649bd120bef9c7f29 Mon Sep 17 00:00:00 2001
From: Carl Love <[EMAIL PROTECTED]>
Date: Fri, 8 Aug 2008 15:38:36 -0700
Subject: [PATCH] powerpc/cell/oprofile: fix mutex locking for spu-oprofile
The issue is the SPU code is not holding the kernel mutex lock while
adding sa
On Wednesday 15 October 2008, Robert Richter wrote:
> there are still these OProfile patches for powerpc pending:
>
> Carl Love (1):
> powerpc/cell/oprofile: fix mutex locking for spu-oprofile
>
> Roel Kluin (1):
> powerpc/cell/oprofile: vma_map: fix test on overlay_tbl_offset
>
> Ca
Ben,
there are still these OProfile patches for powerpc pending:
Carl Love (1):
powerpc/cell/oprofile: fix mutex locking for spu-oprofile
Roel Kluin (1):
powerpc/cell/oprofile: vma_map: fix test on overlay_tbl_offset
Can you or Paul send them upstream? You can pull from here:
git:/
On Wed, 2008-10-15 at 13:46 +0200, Geert Uytterhoeven wrote:
> On Wed, 15 Oct 2008, Benjamin Herrenschmidt wrote:
> > > > Well, at the time of the sample, the other CPU indeed -seems- to be in
> > > > an IRQ disabled section yes.
> > >
> > > This is not really a sample. The hardirqs enable/disabl
On Wed, 2008-10-15 at 14:05 +0200, Geert Uytterhoeven wrote:
> I guess it's auto-enabled when the decrementer interrupt handler exits?
> So shouldn't there be a `bl trace_hardirqs_on' somewhere?
The interrupts are restored to their previous state on exit of
interrupts via the TRACE_AND_RESTORE_IRQ
On Wed, 2008-10-15 at 05:16 -0700, Jesse Barnes wrote:
> On Monday, October 13, 2008 5:55 pm Benjamin Herrenschmidt wrote:
> > This patch adds support for legacy_io and legacy_mem files in
> > bus class directories in sysfs for powerpc
> >
> > Signed-off-by: Benjamin Herrenschmidt <[EMAIL PROTECTED
These patches add support for selecting page size on PPC 44x.
First one adds support for 16K/64K pages while second one adds support
for 256K pages along with some hacks.
However there are still number of problems:
1. We can't use default PKMAP_BASE definition with 64KB/256KB pages so
we change it
This patch adds support for page sizes bigger than 4K (16K/64K) on
PPC 44x.
Signed-off-by: Yuri Tikhonov <[EMAIL PROTECTED]>
Signed-off-by: Vladimir Panfilov <[EMAIL PROTECTED]>
Signed-off-by: Ilya Yanok <[EMAIL PROTECTED]>
---
arch/powerpc/Kconfig | 26 ---
This patch adds support for 256K pages on PPC 44x along with
some hacks needed for this.
Signed-off-by: Yuri Tikhonov <[EMAIL PROTECTED]>
Signed-off-by: Vladimir Panfilov <[EMAIL PROTECTED]>
Signed-off-by: Ilya Yanok <[EMAIL PROTECTED]>
---
arch/powerpc/Kconfig |8
Remove empty/bogus #else from signal_64.c
Signed-off-by: Michael Neuling <[EMAIL PROTECTED]>
---
arch/powerpc/kernel/signal_64.c |2 --
1 file changed, 2 deletions(-)
Benh: Trivial cleanup patch for 2.6.28...
diff --git a/arch/powerpc/kernel/signal_64.c b/arch/powerpc/kernel/signal_64.c
ind
arch/powerpc/kernel/setup_64.c:447:5: warning: "kernstart_addr" is not defined
arch/powerpc/kernel/setup_64.c:447:5: warning: "kernstart_addr" is not defined
kernel/resource.c: In function '__reserve_region_with_split':
kernel/resource.c:554: warning: format '%llx' expects type 'long long unsig
Some comments for some of these...
On Wed, 2008-10-15 at 21:33 -0700, Andrew Morton wrote:
> kernel/resource.c: In function '__reserve_region_with_split':
> kernel/resource.c:554: warning: format '%llx' expects type 'long long
> unsigned int', but argument 3 has type 'resource_size_t'
> kernel/r
From: Andrew Morton <[EMAIL PROTECTED]>
Date: Wed, 15 Oct 2008 21:33:37 -0700
> kernel/resource.c: In function '__reserve_region_with_split':
> kernel/resource.c:554: warning: format '%llx' expects type 'long long
> unsigned int', but argument 3 has type 'resource_size_t'
> kernel/resource.c:554:
On Wed, 2008-10-15 at 10:47 -0500, Ayman El-Khashab wrote:
Note for people on CC: This is a problem on 460EX on a canyonland using
the 4x port.
> The problem occurs when Linux boots. It sees the switch (and looking
> in /sys/bus/... confirms it), but nothing on the downstream sides of
> the switc
On Wed, 2008-10-15 at 22:02 -0700, David Miller wrote:
> From: Andrew Morton <[EMAIL PROTECTED]>
> Date: Wed, 15 Oct 2008 21:33:37 -0700
>
> > kernel/resource.c: In function '__reserve_region_with_split':
> > kernel/resource.c:554: warning: format '%llx' expects type 'long long
> > unsigned int',
At Wed, 15 Oct 2008 21:33:37 -0700,
Andrew Morton wrote:
>
> sound/soc/soc-dapm.c:1029: warning: 'snd_soc_dapm_connect_input' is
> deprecated (declared at sound/soc/soc-dapm.c:1026)
> sound/soc/soc-dapm.c:1029: warning: 'snd_soc_dapm_connect_input' is
> deprecated (declared at sound/soc/soc-dapm
Joel Schopp writes:
> As for the technical comments, I agree with all of them and will
> incorporate them into the next version.
Mark Nelson is working on new memcpy and __copy_tofrom_user routines
that look like they will be simpler than the old ones as well as being
faster, particularly on Cel
On Wed, 2008-10-15 at 22:02 -0700, David Miller wrote:
> > drivers/dma/ioat_dca.c: In function 'dca_enabled_in_bios':
> > drivers/dma/ioat_dca.c:81: error: implicit declaration of function
> > 'cpuid_eax'
> > drivers/dma/ioat_dca.c: In function 'system_has_dca_enabled':
> > drivers/dma/ioat_dca.c
Dan Williams wrote:
> On Wed, 2008-10-15 at 22:02 -0700, David Miller wrote:
>
>>> drivers/dma/ioat_dca.c: In function 'dca_enabled_in_bios':
>>> drivers/dma/ioat_dca.c:81: error: implicit declaration of function
>>> 'cpuid_eax'
>>> drivers/dma/ioat_dca.c: In function 'system_has_dca_enabled':
From: Brice Goglin <[EMAIL PROTECTED]>
Date: Thu, 16 Oct 2008 08:55:08 +0200
> Dan Williams wrote:
> > On Wed, 2008-10-15 at 22:02 -0700, David Miller wrote:
> >
> >>> drivers/dma/ioat_dca.c: In function 'dca_enabled_in_bios':
> >>> drivers/dma/ioat_dca.c:81: error: implicit declaration of func
48 matches
Mail list logo
