Hi Imre,
On 23.09.2014 11:54, Claudio Thomas wrote:
> On 23.09.2014 11:41, Imre Kaloz wrote:
>> On Tue, 23 Sep 2014 11:10:17 +0200, Claudio Thomas
>> wrote:
>>
>>
>> Well, RB333 is MPC8321, RB600 is MPC8323 and we support the
>> MPC8377EWLAN board, which is MPC8377E :)
>>
>>
>> MPC8306 should b
Hi Imre,
On 23.09.2014 11:41, Imre Kaloz wrote:
>
> On Tue, 23 Sep 2014 11:10:17 +0200, Claudio Thomas
> wrote:
>
>
>
>> The RB600/RB300 uses a MPC8377, the XM1700 uses a MPC8306. They are
>> quite similar, but not equal.
>
> Well, RB333 is MPC8321, RB600 is MPC8323 and we support the
> MPC8377EW
Hi Claudio,
On Tue, 23 Sep 2014 11:10:17 +0200, Claudio Thomas
wrote:
The RB600/RB300 uses a MPC8377, the XM1700 uses a MPC8306. They are
quite similar, but not equal.
Well, RB333 is MPC8321, RB600 is MPC8323 and we support the MPC8377EWLAN board,
which is MPC8377E :)
The main problem
Hi Imre,
On 23.09.2014 09:53, Imre Kaloz wrote:
> Hi Claudio,
>
> On Tue, 23 Sep 2014 09:44:03 +0200, Claudio Thomas
> wrote:
>
>> I would like to add a new device to /target/linux/mpc83xx witch needs a
>> special kernel.
>
> In what way is it special? Why can't the same kernel support your
> boa
Hi Claudio,
On Tue, 23 Sep 2014 09:44:03 +0200, Claudio Thomas
wrote:
I would like to add a new device to /target/linux/mpc83xx witch needs a
special kernel.
In what way is it special? Why can't the same kernel support your board as well?
Last time you've said you are going to re-analyse t
Hi,
I would like to add a new device to /target/linux/mpc83xx witch needs a
special kernel.
As I see in other targets this is done usually by adding a first
subtarget, moving the actual config to it and adding a a first profile.
Is there a special naming convention for the first subtarget?
Should
