joining the thread...
--
Alexey Kardashevskiy
IBM OzLabs, LTC Team
e-mail/sametime: a...@au1.ibm.com
notes: Alexey Kardashevskiy/Australia/IBM
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
joining the thread...
--
Alexey Kardashevskiy
IBM OzLabs, LTC Team
e-mail/sametime: a...@au1.ibm.com
notes: Alexey Kardashevskiy/Australia/IBM
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
On Tue, 4 Jan 2011 17:52:38 -0600
Meador Inge wrote:
> Thanks for the feedback Scott.
>
> On 01/03/2011 02:22 PM, Scott Wood wrote:
> > On Wed, 22 Dec 2010 23:58:09 -0600
> > These nodes cannot go under the mpic node, because interrupt
> > controllers need #address-cells =<0>.
>
> Good point.
Thanks for the feedback Scott.
On 01/03/2011 02:22 PM, Scott Wood wrote:
On Wed, 22 Dec 2010 23:58:09 -0600
These nodes cannot go under the mpic node, because interrupt
controllers need #address-cells =<0>.
Good point. Do they actually need it or is that just the way it
currently is? [1] ma
>
> > Okay, I get that and it makes sense with what I know so far about how
the
> > kernel device model works (which I'm still learning). So how would I
> > manually add a device? Say I create the PCI wrapper driver that
claims
> > the clone-TSEC, is there a "register device" type call simi
On Tue, 4 Jan 2011 22:42:49 +0100
Alexandru Ionut Grama wrote:
> You're right Scott, there's no section in arch/powerpc/boot/Makefile
> involving dts file for mpc8272ads.
>
> Well some time ago I've already write an email explaining that I've try to
> port a custom board patch from 2.6.21 to 2.6
You're right Scott, there's no section in arch/powerpc/boot/Makefile
involving dts file for mpc8272ads.
Well some time ago I've already write an email explaining that I've try to
port a custom board patch from 2.6.21 to 2.6.35. I can't make the changes
properly in 2.6.35, so that's why I've decide
Hi there,
I'm using the Canyonlands evaluation board for the ppc 460ex processor. I want
to access the GPIO pins, set its direction and set/get their values.
Is there is any common driver to do so? I went throught the
Documentation/gpio.txt and the arch/powerpc/sysdev/ppc4xx_gpio.c but I don't
On Tue, 4 Jan 2011 13:00:07 -0800
bruce_leon...@selinc.com wrote:
> True, but we really didn't want to recreate all the infrastructure
> that the gianfar driver has in it we wanted to just use it. Maybe
> what I should do is just take the guts of the gianfar driver and make
> a pure PCI driver ou
On Tue, 4 Jan 2011 13:00:07 -0800
wrote:
> Okay, I get that and it makes sense with what I know so far about how the
> kernel device model works (which I'm still learning). So how would I
> manually add a device? Say I create the PCI wrapper driver that claims
> the clone-TSEC, is there a "r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 29.12.2010, at 20:51, Peter Tyser wrote:
> Previously SPRGs 4-7 were improperly read and written in
> kvm_arch_vcpu_ioctl_get_regs() and kvm_arch_vcpu_ioctl_set_regs();
>
> Signed-off-by: Peter Tyser
Thanks a lot for the catch. At least for Boo
On Tue, 2011-01-04 at 13:23 -0600, Scott Wood wrote:
> On Tue, 4 Jan 2011 10:58:35 -0800
> wrote:
>
> > Hi all,
> >
> > I'm working on a project with an MPC8347 and three ethernet ports. Because
> > of end of life issues we've had to replace the part we're using for the
> > third ethernet port
Scott,
Thanks for the feedback.
>
> Making a faithful clone of any reasonably complex device strikes me as
> more work than writing a new ethernet driver.
>
> The last thing you want to end up doing is...
>
> > And for speed sake it would go on the PCI bus.
> > (So much for letting HW make d
On 12/23/2010 01:49 PM, Meador Inge wrote:
>
> We can't just remove the IRQ of the _other_ OS from the 'interrupts'
> property in the message node because we need to know the IRQ in order
> to talk to the other OS. So, we use protected sources to tell the OS
> that an IRQ is not available for i
On Tue, 4 Jan 2011 10:58:35 -0800
wrote:
> Hi all,
>
> I'm working on a project with an MPC8347 and three ethernet ports. Because
> of end of life issues we've had to replace the part we're using for the
> third ethernet port and we decided rather than rely on a vendor who would
> pull a part
Hi all,
I'm working on a project with an MPC8347 and three ethernet ports. Because
of end of life issues we've had to replace the part we're using for the
third ethernet port and we decided rather than rely on a vendor who would
pull a part out from under us every two to three years we would do
On Tue, Jan 04, 2011 at 09:31:32AM -0500, Josh Boyer wrote:
> On Tue, Jan 04, 2011 at 07:30:30AM -0700, Grant Likely wrote:
> >On Tue, Jan 04, 2011 at 08:59:31AM -0500, Josh Boyer wrote:
> >> On Mon, Jan 03, 2011 at 02:07:40PM -0700, Grant Likely wrote:
> >> >Signed-off-by: Grant Likely
> >> >---
On Tue, Jan 04, 2011 at 07:30:30AM -0700, Grant Likely wrote:
>On Tue, Jan 04, 2011 at 08:59:31AM -0500, Josh Boyer wrote:
>> On Mon, Jan 03, 2011 at 02:07:40PM -0700, Grant Likely wrote:
>> >Signed-off-by: Grant Likely
>> >---
>> >
>> >I'm picking this one up immediately into my next-devicetree b
On Tue, Jan 04, 2011 at 08:59:31AM -0500, Josh Boyer wrote:
> On Mon, Jan 03, 2011 at 02:07:40PM -0700, Grant Likely wrote:
> >Signed-off-by: Grant Likely
> >---
> >
> >I'm picking this one up immediately into my next-devicetree branch
>
> Hm. So these are of course correct, and with that:
>
>
On Mon, Jan 03, 2011 at 03:06:03PM -0700, Grant Likely wrote:
>Signed-off-by: Grant Likely
>---
>
>I'm putting this patch into my next-devicetree branch.
Acked-by: Josh Boyer
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozl
On Mon, Jan 03, 2011 at 02:07:40PM -0700, Grant Likely wrote:
>Signed-off-by: Grant Likely
>---
>
>I'm picking this one up immediately into my next-devicetree branch
Hm. So these are of course correct, and with that:
Acked-by: Josh Boyer
but I do wonder how you noticed them? DTC didn't throw
21 matches
Mail list logo