public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Artem B. Bityutskiy" <dedekind@yandex.ru>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: manningc2@actrix.gen.nz, linux-mtd@lists.infradead.org
Subject: Re: MTD git repository status
Date: Tue, 08 Nov 2005 17:10:52 +0300	[thread overview]
Message-ID: <4370B1EC.8000504@yandex.ru> (raw)
In-Reply-To: <200511071915.03263.tglx@linutronix.de>



Thomas Gleixner wrote:
> - [MTD] NAND: OOB changes
> 	Needs more thoughts. I'm particularly unhappy with the introduction of new 
> functions and the still pending problem of the automatic placement/retrieval 
> of oob data. The change should subsume and/or extend the oob_info 
> functionality rather than introducing a parallel solution.

As for me, the ideal would be to have:
1. a method to fetch the number of OOB bytes available for user;
2. a method of read/write a buffer of that length to/from OOB; that 
space may be non-contiguous, but this should be hidden from the user.

Complications like the need to supply oob_info look unreasonable to me. 
Most (may be all?) people don't care about the OOB layout and just want 
to read/write data from/to it. So, I agree with Charles.

Any example of when users want to know the oob layout? May be nanddump 
utilities? Not sure.

-- 
Best Regards,
Artem B. Bityutskiy,
St.-Petersburg, Russia.

  parent reply	other threads:[~2005-11-08 14:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-07 18:15 MTD git repository status Thomas Gleixner
2005-11-07 19:24 ` Thomas Gleixner
2005-11-07 19:26 ` Charles Manning
2005-11-11  6:57   ` Vitaly Wool
2005-11-07 20:43 ` Vitaly Wool
2005-11-07 21:33   ` MTD git repository status ==> oob_info & other methods Charles Manning
2005-11-08 14:10 ` Artem B. Bityutskiy [this message]
2005-11-08 20:03   ` MTD git repository status Charles Manning

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4370B1EC.8000504@yandex.ru \
    --to=dedekind@yandex.ru \
    --cc=linux-mtd@lists.infradead.org \
    --cc=manningc2@actrix.gen.nz \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox