Hello.

Nori, Sekhar wrote:

Either way, the lack of a complete proposal (not necessarily
in the form of patches) makes it hard to get anywhere with
such OMAP-L1xx discussions...
 think I've expressed it clear enough: common shared code is
to be moved to plat-davinci/ and OMAP-L1x support is to be
added into new mach- directory.
nd yet Kevin felt that was missing details (not complete)...

While that sounds plausible to me at this point, it's also
clear that the missing details could make a big difference.

I suspect that until patches appear, discussion can get no
further.  Plus, if it's going to be "mach-omap-L1" it'd
be good to have enough detail that the OMAP team (and RMK)
can see why it should pair with "plat-davinci" instead of
the more obvious "plat-omap".
egarding the name
------------------

I really don't like the omap creep that's happening.  The da830 is
  Who does? :-)
based on davinci and not at all on an omap so I'd like to keep it
contained as possible.  TI has expressed a strong desire to have
both so our current plan is the rename the defconfig
to "da830_omapl137_defconfig" and menuconfig text options to say
"DA830/OMAP-L137...".  I don't know if this will be acceptable to the
community.

   I'm afraid there's nothing explaining why it's DA830 now, with chip
marking having been changed to XD830 and that model name not being
mentioned anywhere in documentation...
The part is being called DA830 in TI websites 
(http://focus.ti.com/apps/docs/gencontent.tsp?contentId=52385&appId=1). I am 
not sure if documentation with DA830 name is going to be made public. I can ask 
around.

Just try searching for the part number TMS302DA830 and the search won't yield anything.

Thanks,
Sekhar

WBR, Sergei



_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Reply via email to