[PATCH 0/3] Maverick ti-omap4, Modularize syslink drivers

[Tim Gardner]

On 06/30/2010 03:38 AM, Sebastien Jan wrote:
> Looping Mathieu and Nicolas
>
> + See my answers inlined
>
> On 06/30/2010 11:21 AM, Bryan Wu wrote:
>> On 06/30/2010 03:25 AM, Tim Gardner wrote:
>>> Bryan,
>>>
>>> TI is interested in modularizing some of the syslink drivers. The
>>> first 2 patches are required before that can be done. Please have
>>> a look to make sure its the right thing to do. I assume the right
>>> way to get everything loaded is to add notify_ducatidriver to
>>> /etc/modules.
>>>
>>
>> Sebjan, will you confirm this request? IIRC, you mentioned we need
>> built-in syslink driver before. And if we modularize it, does TI
>> notice this failure which Tim fixed in this patchset?
>
> Yes: up to now, our syslink driver used to be statically linked
> mainly because it did not support beeing built as a module. After
> working with our dev team, this is now fixed. I have just push some
> patches for that in our dev.omapzoom tree.
>
> Now we were wondering which was the best way to auto install the
> syslink driver modules in the system, hence the discussion with
> Mathieu and Tim.
>
> I did not try yet any auto install strategy, and have not seen the
> patches from Tim, so I cannot comment further.
>

Auto installing won't be a kernel patch. As Oliver suggested, we can add 
the platform module name to /etc/modules during install, or as Loic 
suggested we can write an upstart job to load it at boot time. I don't 
have a strong preference.

rtg
-- 
Tim Gardner tim.gardner at canonical.com