Le mercredi 20 décembre 2006 à 16:55 +0000, [EMAIL PROTECTED] a écrit : > -------------- Original message ---------------------- > From: Patrick McNamara <[EMAIL PROTECTED]> > > > > > > > > So, basically, I think the pins on a chip are a licensing boundary. > > And it goes further. What if a company buys a bunch of TRV10 chips > > and embeds them in a high end phone/pda that is otherwise a closed > > design? > > > I'd say that's an entirely proper thing for them to do. If they don't > sign a > proprietary license agreement with Traversal, about the most they'd be > obligated to do is include a URL in the product literature, pointing to > the TRV10 documentation download site as a consequence of physically > distributing a part received under an open hardware license. > Embedded products are part of the TRV10's target market. > From a strategic viewpoint, anybody who buys open-design hardware > parts for any reason helps build up volume and bring down piece parts > costs, and that helps all of us. Anything that increases the popularity of > an open-design part helps our general credibility -- so we want the world > to know where the part is used. I would note that this is not just a strategic viewpoint but rather the specificity of the hardware, that is to say, the componment and more generally the part. A simple question, why this discussion about open source drivers comes here ? Should I understand that when somebody speaks about this, then open hardware is the solution, the first thing that comes in our mind ? Okay, but here, when one is discussing about open hardware, one refers mainly to free software or OSS and one tends to let aside the specificity of the hardware, what is different from software.
It's just my personnal feeling but there is something like a split: when it's about software for hardware e.g a driver, the answer should be find in open hardware; but when it's about hardware the answer should be find in free software. That sounds good just because that sounds complementary but nothing else, otherwise the link to the hardware's specificities is missing. > _______________________________________________ > Open-graphics mailing list > [email protected] > http://lists.duskglow.com/mailman/listinfo/open-graphics > List service provided by Duskglow Consulting, LLC (www.duskglow.com) > _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
