public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Ollie Lho <ollie@sis.com.tw>
To: "Carson, Jon A." <JACarson@addcoinc.com>
Cc: "'mtd@infradead.org'" <mtd@infradead.org>,
	"Meyers, Jerry M." <JMMeyers@addcoinc.com>
Subject: Re: Still having problems with nftl_format
Date: Wed, 25 Apr 2001 16:41:58 +0800	[thread overview]
Message-ID: <3AE68DD6.382351AC@sis.com.tw> (raw)
In-Reply-To: 5B08DC7C9AA6D411930E00105A19794B3E2405@EXCHANGE

"Carson, Jon A." wrote:
> 
> Hi,
> 
> A while back ( April 9, 2001 ) , I reported a problem with nftl_format. I
> know you are busy, but I wanted to state the problem again and also add some
> new information.
> 
> The problem is that everything is nice until it gets to Phase 3 which deals
> with writing some data into the chip.
> 
> I plugged in some printf's that show the state of the variables of interest,
> before we drop into the "for" loop.  I also added a printf to the for loop
> in case something was sucessful.  Please note that the first time through
> the loop, the call to the "ioctl" was apparently sucessful.  Every call to
> the same ioctl after that failed with errno == 14  (Bad address) .  I have
> included an excerpt from the nftl_format.c showing the revesion level of the
> code that I am using.
> 

Did you CVS update and recompile BOTH the driver and nftl_format ?? The
problem is in a change in *Kernel Header* file. So you must update and
recompile everything.

Ollie


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

      reply	other threads:[~2001-04-25 12:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-24 18:25 Still having problems with nftl_format Carson, Jon A.
2001-04-25  8:41 ` Ollie Lho [this message]

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=3AE68DD6.382351AC@sis.com.tw \
    --to=ollie@sis.com.tw \
    --cc=JACarson@addcoinc.com \
    --cc=JMMeyers@addcoinc.com \
    --cc=mtd@infradead.org \
    /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