Re[2]: [PATCH 1/2] Introduce device_platform_driver() macro

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

 



...
> > Besides, as far as I know currently we are not using __init section.
> > Can we define this one in the linker script and release this memory after
> > initialization is complete?
> 
> What would you do then with the memory afterwards? The tlsf allocator
> supports memory pools, so in theory we could use it, but adding support
> for this to barebox would probably eat up more space in the binary than
> you could safe with the few initcalls.

Not just a few initcalls. We can put there boards initialization code,
as is done in the kernel.
Well, drop this question for now.
Thanks!

---
_______________________________________________
barebox mailing list
barebox@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/barebox


[Index of Archives]     [Linux Embedded]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux