On Thu, Oct 23, 2008 at 03:43:58PM +1100, Benjamin Herrenschmidt wrote:
> On Wed, 2008-10-22 at 17:59 +0200, Ingo Molnar wrote:
> > * Nick Piggin <[EMAIL PROTECTED]> wrote:
> >
> > > Speed up generic mutex implementations.
> > >
> > > - atomic operations which both modify the variable and return
On Thu, 23 Oct 2008 17:29:38 +1100
Stephen Rothwell <[EMAIL PROTECTED]> wrote:
> Hi Alan,
>
> Today's linux-next build (powerpc ppc64_defconfig) failed like this:
>
> drivers/char/hvc_console.c: In function 'hvc_set_winsz':
> drivers/char/hvc_console.c:532: warning: passing argument 2 of
> 'tty
On Thu, 2008-10-23 at 08:34 +0100, Alan Cox wrote:
>
> Patch is correct.
>
> Do the hvc patches have dependancies on the PPC tree as well as the
> tty tree ?
Note that I have a serie of 5 hvc patches in the ppc tree...
Ben.
___
Linuxppc-dev mailing
On Wed, 22 Oct 2008 15:34:52 -0500 Milton Miller <[EMAIL PROTECTED]> wrote:
>
> On Oct 22, 2008, at 9:36 AM, Sebastien Dugue wrote:
>
> >
> > The 'ibm,interrupt-server#-size' properties are not cpu nodes
> > properties,
> > but rather live under the interrupt source controller nodes (compatib
Hello
When I do make menuconfig I get following error :-
"
*** Unable to find the ncurses libraries or the
*** required header files.
*** 'make menuconfig' requires the ncurses libraries.
***
*** Install ncurses (ncurses-devel) and try again.
***
make[1]: *** [scripts/kconfig/doche
Am Donnerstag 23 Oktober 2008 11.10:50 schrieb Dudeja, Ashish:
> Hello
>
> When I do make menuconfig I get following error :-
>
>
>
> "
>
> *** Unable to find the ncurses libraries or the
>
> *** required header files.
>
> *** 'make menuconfig' requires the ncurses libraries.
>
> ***
>
> *** In
On Thu, Oct 23, 2008 at 05:29:38PM +1100, Stephen Rothwell wrote:
> drivers/char/hvc_console.c: In function 'hvc_set_winsz':
> drivers/char/hvc_console.c:532: warning: passing argument 2 of
> 'tty_do_resize' from incompatible pointer type
> drivers/char/hvc_console.c:532: error: too many arguments
When saving an older signal context (smaller context without the extra
VSX state) for a task that has used VSX, currently we'll EINVAL.
Unfortunately if we have an older program which doesn't know about the
newer expanded signal context but happens to execute some VSX
instructions (via some new lib
On Thu, Oct 09, 2008 at 01:57:37PM +1100, Paul Mackerras wrote:
>Josh Boyer writes:
>
>> From: Josh Poimboeuf <[EMAIL PROTECTED]>
>>
>> The powerpc 32-bit and 64-bit kernel_thread functions don't properly
>> propagate errors being returned by the clone syscall. (In the case of
>> error, the sysca
The GPIOLIB allows the specification of a base gpio number for a
controller. That is not possible using OF. Instead, free gpio numbers
are assigned.
In order to allow static, predefined gpio numbers, a base property in
the gpio controller node specifies the first gpio number.
Signed-off-by: Wolfg
On Thursday 23 October 2008 15:52:28 Stephen Rothwell wrote:
> Hi Rusty,
>
> Today's linux-next build (powerpc ppc64_defconfig) failed like this:
>
> arch/powerpc/platforms/cell/spu_base.c: In function
> 'mm_needs_global_tlbie': arch/powerpc/platforms/cell/spu_base.c:117: error:
> implicit declarat
Hi,
Andreas (Cc'ed) asked whether it was possible to use snd-aoa on his
machine, a PowerMac3,6. It appears that it is fairly easy since the
machine seems to use a regular i2sbus.
To identify it, after looking through my device-tree collections I think
that the "device-id" property of the sound no
On Oct 23, 2008, at 7:27 AM, Wolfgang Ocker wrote:
The GPIOLIB allows the specification of a base gpio number for a
controller. That is not possible using OF. Instead, free gpio numbers
are assigned.
In order to allow static, predefined gpio numbers, a base property in
the gpio controller node
The GPIOLIB allows the specification of a base gpio number for a
controller. That is not possible using OF. Instead, free gpio numbers
are assigned.
In order to allow static, predefined gpio numbers, a base property in
the gpio controller node specifies the first gpio number.
v2: added descriptio
On Oct 23, 2008, at 9:30 AM, Wolfgang Ocker wrote:
--- linux-2.6.27.2/Documentation/powerpc/booting-without-
of.txt.of_gpiospecbase 2008-10-18 19:57:22.0 +0200
+++ linux-2.6.27.2/Documentation/powerpc/booting-without-of.txt
2008-10-23 16:23:07.0 +0200
@@ -2580,12 +2582,17 @@
The GPIOLIB allows the specification of a base gpio number for a
controller. That is not possible using OF. Instead, free gpio numbers
are assigned.
In order to allow static, predefined gpio numbers, a base property in
the gpio controller node specifies the first gpio number.
v2, v3: added/improv
Hi Milton,
My suggestions:
Milton Miller wrote:
The __kdump_flag ABI is overly constraining for future development.
As of 2.6.27, the kernel entry point has 4 constraints: Offset 0 is
the starting point for the master (boot) cpu (entered with r3 pointing
to the device tree structure), offse
This adds a SPI driver for the SPI controller found in the IBM/AMCC
4xx PowerPC's.
Signed-off-by: Stefan Roese <[EMAIL PROTECTED]>
---
drivers/spi/Kconfig |7 +
drivers/spi/Makefile |1 +
drivers/spi/spi_ppc4xx.c | 550 ++
3 files chan
On Thu, Oct 23, 2008 at 03:44:21PM +0200, Johannes Berg wrote:
> Hi,
>
> Andreas (Cc'ed) asked whether it was possible to use snd-aoa on his
> machine, a PowerMac3,6. It appears that it is fairly easy since the
> machine seems to use a regular i2sbus.
>
> To identify it, after looking through my
On Thu, 2008-10-23 at 17:35 +0200, Gabriel Paubert wrote:
> On my almost 8 years old PowerMac (PowerMac3,4 accorfing to OF):
>
> $ find /proc/device-tree/ -wholename '*sound/device-id' | xargs hd
> 00 00 00 0e ||
> 0004
>
> or 14 in decimal
On Thu, Oct 23, 2008 at 05:41:02PM +0200, Johannes Berg wrote:
> On Thu, 2008-10-23 at 17:35 +0200, Gabriel Paubert wrote:
>
> > On my almost 8 years old PowerMac (PowerMac3,4 accorfing to OF):
> >
> > $ find /proc/device-tree/ -wholename '*sound/device-id' | xargs hd
> > 00 00 00 0e
On Thursday 23 October 2008, Wolfgang Ocker wrote:
> The GPIOLIB allows the specification of a base gpio number for a
> controller. That is not possible using OF. Instead, free gpio numbers
> are assigned.
>
> In order to allow static, predefined gpio numbers, a base property in
> the gpio controll
I tried booting a post 2.6.27 -git on a Motorola ATCA6101 (very similar to a
Maple board). The first time I booted I got the first log below via the
serial console. I rebooted and got as far as a login prompt. I was able to
log in via the serial console, but then got an almost identical oops
On Thu, 2008-10-23 at 18:43 +0200, Gabriel Paubert wrote:
>
> Yes, on a pristine 2.6.27 kernel right now.
>
> > Can you tell me which devices it has, like does it have line-in,
> > microphone, headphones, ...?
>
> I'm not an audio specialist, so the symbols used to
> identify the ports look like
Hi guys,
I'm a little perplexed as to how I would define a GPIO
controller in a device tree but mark off pins as available or
not, so users can geek around in their own drivers without
defining in a device tree exactly what they intend to use it
for (especially if it's something really weird)
Kumar Gala wrote:
On Oct 23, 2008, at 7:27 AM, Wolfgang Ocker wrote:
The GPIOLIB allows the specification of a base gpio number for a
controller. That is not possible using OF. Instead, free gpio numbers
are assigned.
In order to allow static, predefined gpio numbers, a base property in
the
On Thu, 23 Oct 2008 23:41:48 +0200
Christoph Hellwig <[EMAIL PROTECTED]> wrote:
> +#ifdef CONFIG_IBM_NEW_EMAC_NO_FLOW_CONTROL
> dev->features |= EMAC_FTR_NO_FLOW_CONTROL_40x;
> +#else
> + printk(KERN_ERR "%s: Flow control not disabled!\n",
> +
Chris Friesen wrote:
> I tried booting a post 2.6.27 -git on a Motorola ATCA6101 (very
> similar to a Maple board). The first time I booted I got the first
> log below via the serial console. I rebooted and got as far as a
> login prompt. I was able to log in via the serial console, but then
> g
+#ifdef CONFIG_IBM_NEW_EMAC_NO_FLOW_CONTROL
dev->features |= EMAC_FTR_NO_FLOW_CONTROL_40x;
+#else
+ printk(KERN_ERR "%s: Flow control not disabled!\n",
+ np->full_name);
+ return -ENXIO;
+#endi
Am Donnerstag 23 Oktober 2008 15.44:21 schrieb Johannes Berg:
Hi Johannes
My wife has a PowerBook with exactly the machine you are looking for.
(Running Linux pb 2.6.24-19-powerpc #1 Fri Jul 11 21:37:37 UTC 2008 ppc
GNU/Linux)
Therefore here the following info.
cat /proc/cpuinfo
processor
You could have the gpio node define an "address space" where each
"address" is a GPIO pin number.
The node would have one address cell and one size cell, and the
"decode-unit" and "encode-unit" methods would be the garden-variety
flavors that just convert integers between binary and ASCII. Si
Mitch Bradley wrote:
[snip]
You could adopt the convention that preassigned GPIOs must be
represented by subordinate nodes, and any GPIO that is not covered by a
subordinate node's "reg" property is implicitly available. That's the
way it works for other address spaces.
I like that idea e
i2c is broken on linkstation / kurobox machines since at least 2.6.27. Fix
it. Also remove CONFIG_SERIAL_OF_PLATFORM, which, if enabled, breaks the
serial console after the "console handover: boot [udbg0] -> real [ttyS1]"
message.
Signed-off-by: Guennadi Liakhovetski <[EMAIL PROTECTED]>
---
N
From: "Brandeburg, Jesse" <[EMAIL PROTECTED]>
Date: Thu, 23 Oct 2008 14:50:06 -0700
> Chris Friesen wrote:
> > I tried booting a post 2.6.27 -git on a Motorola ATCA6101 (very
> > similar to a Maple board). The first time I booted I got the first
> > log below via the serial console. I rebooted a
On Fri, 2008-10-24 at 01:05 +0200, Guennadi Liakhovetski wrote:
> i2c is broken on linkstation / kurobox machines since at least 2.6.27. Fix
> it. Also remove CONFIG_SERIAL_OF_PLATFORM, which, if enabled, breaks the
> serial console after the "console handover: boot [udbg0] -> real [ttyS1]"
> me
Mitch Bradley wrote:
[snip]
You could adopt the convention that preassigned GPIOs must be
represented by subordinate nodes, and any GPIO that is not covered by
a subordinate node's "reg" property is implicitly available. That's
the way it works for other address spaces.
I like that idea e
On Thu, 23 Oct 2008 15:49:32 -0700
Ira Snyder <[EMAIL PROTECTED]> wrote:
> This adds support to Linux for a virtual ethernet interface which uses the
> PCI bus as its transport mechanism. It creates a simple, familiar, and fast
> method of communication for two devices connected by a PCI interface
On Thu, Oct 23, 2008 at 12:22:03PM -1000, Mitch Bradley wrote:
> You could have the gpio node define an "address space" where each
> "address" is a GPIO pin number.
>
> The node would have one address cell and one size cell, and the
Not necessarily. If you were to have such an address space,
On Thu, Oct 23, 2008 at 02:52:18PM -1000, Mitch Bradley wrote:
>>
>>
>> Mitch Bradley wrote:
>> [snip]
>>
>>> You could adopt the convention that preassigned GPIOs must be
>>> represented by subordinate nodes, and any GPIO that is not covered by
>>> a subordinate node's "reg" property is implici
This patch adds a new backend for the hvc console based on the
low-level udbg callbacks. This effectively implements a working
runtime console in terms of the simple udbg primitives. This is kind
of a hack - since udbg isn't something you really want to be using
routinely - but it's really useful
Resources for PHB's that are DLPAR added to a system are not acquired.
Not having these resources allocated causes an oops during DLPAR
remove of the PHB when we try to release non-existant resources.
The patch appears a bit messy, this is mainly due to moving everything
one tab to the left in th
No, no, no, no, no. Making complex multi-level representations of
nested things for gpios is just insanity.
You know, I don't find this "argument" particularly compelling. But it
certainly is strongly worded.
Just use the same encoded
format as we already use for gpio descriptors in 'g
From: Milton Miller <[EMAIL PROTECTED]>
The __kdump_flag ABI is overly constraining for future development.
As of 2.6.27, the kernel entry point has 4 constraints: Offset 0 is
the starting point for the master (boot) cpu (entered with r3 pointing
to the device tree structure), offset 0x60 is c
On Thu, Oct 23, 2008 at 06:17:45PM -1000, Mitch Bradley wrote:
>>
>> No, no, no, no, no. Making complex multi-level representations of
>> nested things for gpios is just insanity.
>
>
> You know, I don't find this "argument" particularly compelling. But it
> certainly is strongly worded.
>
>>
Hi Alan, Hendrik,
On Thu, 23 Oct 2008 08:34:06 +0100 Alan Cox <[EMAIL PROTECTED]> wrote:
>
> On Thu, 23 Oct 2008 17:29:38 +1100
> Stephen Rothwell <[EMAIL PROTECTED]> wrote:
>
> > Hi Alan,
> >
> > Today's linux-next build (powerpc ppc64_defconfig) failed like this:
> >
> > drivers/char/hvc_cons
On Thu, Oct 23, 2008 at 06:05:19PM -0500, Matt Sealey wrote:
>
>
> Mitch Bradley wrote:
> [snip]
>
>> You could adopt the convention that preassigned GPIOs must be
>> represented by subordinate nodes, and any GPIO that is not covered by a
>> subordinate node's "reg" property is implicitly availa
The block layer dropped the virtual merge feature
(b8b3e16cfe6435d961f6aaebcfd52a1ff2a988c5). BIO_VMERGE_BOUNDARY
definition is meaningless now (For POWER, BIO_VMERGE_BOUNDARY has been
meaningless for a long time since POWER disables the virtual merge
feature).
Signed-off-by: FUJITA Tomonori <[EMA
47 matches
Mail list logo
