On Mon, 2013-12-02 at 17:05 +, Gupta, Pekon wrote:
(2) Also selection of ecc-scheme mainly depends on NAND device parameter
(like density, page-size, oobsize) which remain constant for a device
(all NAND partitions). Thus all partitions should use *same* ecc-scheme
preferable
On 02/21/2013 05:11:06 PM, Jason Gunthorpe wrote:
On Thu, Feb 21, 2013 at 05:05:54PM -0500, Nicolas Pitre wrote:
No it is not. FIT is about bundling a multi-platform kernel with a
bunch of DTBs together in a single file. I don't think you need
that
for your embedded system. The wrong
On 09/28/2011 03:15 AM, Cousson, Benoit wrote:
On 9/27/2011 7:40 AM, Nayak, Rajendra wrote:
On Monday 26 September 2011 10:20 PM, Benoit Cousson wrote:
+Required properties:
+- compatible:
+ - ti,omap2-gpio for OMAP2 and OMAP3 controllers
Would it be more readable to have
ti,omap2-gpio
On 09/28/2011 03:57 PM, Cousson, Benoit wrote:
On 9/28/2011 8:23 PM, Scott Wood wrote:
What does the id mean, in relation to the actual hardware?
It's true that the description is not super meaningful...
This is the HW instance number. We have 6 gpios, named gpio1 to gpio6,
but the pin
On 08/09/2011 08:52 PM, David Gibson wrote:
Of course, the problem with reg-names is that it will be ignored by
older OSes, and so 'reg' must still be in the correct order. In which
case you could argue it's more sensible to just have a static place to
name mapping in the Linux driver.
I
On 08/09/2011 12:47 PM, Cousson, Benoit wrote:
On 8/9/2011 7:23 PM, Grant Likely wrote:
There is no analogous mechanism for _byname in the device tree. The
DT binding for a device must explicitly state what order the register
ranges are in. The driver will need to be adapted.
That seems
On 08/09/2011 04:44 PM, Cousson, Benoit wrote:
OK, so what about extending the reg attribute to be a reg node?
dev {
reg {
name = foo_wrapper;
start = 0x1;
end = 0x200;
}
reg {
name = foo;
start = 0x2;
end = 0x200;
