Re: [Ksummit-2013-discuss] ARM topic: Is DT on ARM the solution, or is there something better?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Wed, 2013-10-23 at 19:45 +0200, Richard Cochran wrote:
> 
> Once I design my board, and it goes into production, the hardware is
> fixed. It doesn't change, and neither should the description of the
> hardware, also known as the DTB. If I have to research all of the
> ways 

SOC support are never completely finished; subsystems are getting new
features.
 
It's possible to ship a product with a kernel version that does not
handle all the chip goodies, then want to upgrade the kernel later when
someone has written the driver for a previously unused hardware block.

the first iteration of your DTB would be incomplete, the bindings to
describe that hardware block would not exist inside it.

real life example with Marvell Kirkwood, hw crypto support was added 1
year after initial SOC support.

I'm happy I can use it now on existing boards by "just" upgrading the
kernel.

-- 
Maxime


--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Device Tree Compilter]     [Device Tree Spec]     [Linux Driver Backports]     [Video for Linux]     [Linux USB Devel]     [Linux PCI Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Yosemite Backpacking]
  Powered by Linux