Hello Wolfram,
Wolfram Sang wrote:
> On Sat, Dec 04, 2010 at 09:21:54AM +0100, Heiko Schocher wrote:
>
> There shall be only one mpc5200-defconfig. Does the genric one work with your
> board?
Just tried, mpc5200_defconfig works for me, but...
... I miss there the LM81 and RTC DS1374 support ...
Hello Wolfram,
Wolfram Sang wrote:
> On Mon, Dec 06, 2010 at 07:29:23AM +0100, Heiko Schocher wrote:
>
>> Thanks for the review,
>
> You're welcome. Oh, just to make sure: It is really a MPC5200 and not a
> MPC5200B?
Yep, it is a MPC5200
bye,
Heiko
--
DENX Software Engineering GmbH, MD: W
On Mon, Dec 06, 2010 at 07:29:23AM +0100, Heiko Schocher wrote:
> Thanks for the review,
You're welcome. Oh, just to make sure: It is really a MPC5200 and not a
MPC5200B?
Kind regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang|
Industrial Linux So
Hello Wolfram,
Wolfram Sang wrote:
> On Sat, Dec 04, 2010 at 09:21:46AM +0100, Heiko Schocher wrote:
>> - MPC5200
>> - serielle console on PSC 1
>
> serial
Hups, thanks!
>> - 128MiB RAM
>> - 32MiB NOR Flash
>> - FEC Ethernet
>> - 2 I2C Busses
>> - FPGA on CS3 accessed through mtd-ram
>> - ATA
>
Hi Michael,
> So you have a device, it appears in your device tree, and you want to
> write a driver for it.
Nice write up, mind if I steal this for the devicetree.org wiki?
Cheers,
Jeremy
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
h
On Fri, 2010-12-03 at 15:58 +0100, Guillaume Dargaud wrote:
> > No. of_platform_drivers are more/less obsolete. Normal platform drivers
> > can now be associated with a device-tree node just fine.
>
> OK.
>
> If my dts definition is thus:
> xps_acqui_data_0: xps-acqui-d...@c980
> Your snd-aoa seems to support PowerMac3,4. Is it really tested?
I used to add only IDs that some people tested, until most things worked
and I wholesale added all of the ones found in Darwin.
> The reason I'm asking: people are having problems with sound on that
> machine. Even snd-powermac di
The therm_pm72 driver, used on the PowerMac G5 range, cannot be
auto-loaded, since the driver itself creates both the device node
and the driver instance.
Moving the device node creation to the platform setup code and
adding the necessary MODULE_DEVICE_TABLE() information allows the
driver to be a
