Re: M5282 Coldfire & I2C

Hello Steven,

It's not working. I with printk() I can see that the module_init is called,
but the mfci2c_probe() never gets called. So platform_driver_probe() does
nothing??.

Regards,
Nic


On Fri, Jun 27, 2014 at 3:31 PM, Steven King <[email protected]> wrote:

> On Friday 27 June 2014 12:43:34 am Nic Roets wrote:
> > A few years ago we developed a board closely based  on the M5282EVB.
> > uClinux at that time included the 2.6 kernel. Everything, including i2c
> > worked with only minor customization.
> >
> > Now I'm trying to update to the latest uClinux-dist. On some issues, I've
> > seen improvements, such as removal of references to the MBAR register
> > (which the processor does not have IIRC).
> >
> > But it looks like the i2c driver has not been maintained and no longer
> > compiles with the 3.x kernel. I also tried Steven Kings patch, but it
> seems
> > to be aimed at a different processor.
> >
> > Is it fair to conclude that the M5282 port of the 3.x kernel is still "in
> > development" ?
> >
> > And to conclude that the stable kernel for the M5282 is linux 2.6 ?
> Hi Nic,
>
> My I2C patch was actually originally developed for the m5282 and should
> work
> for any coldfire part with a I2C/IIC module.
>
> The 5282, along with the 5253, the 5484 and the 54418 are the parts I have
> boards for and any code I've submitted usually has been tested on all 4.  I
> usually test new kernel releases (when I have the time and patience) on
> all 4
> so I'd consider the m5282 port to be as current any of the
> coldfire/m68knommu
> in the 3.x kernels.
>



-- 
Regards,
Nic

_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev