public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Ho-Kuo Chan" <hchan@wavesat.com>
To: "David Woodhouse" <dwmw2@infradead.org>
Cc: <linux-mtd@lists.infradead.org>
Subject: Re: Trouble indetifying FLASH part
Date: Thu, 16 May 2002 10:52:14 -0400	[thread overview]
Message-ID: <009c01c1fce9$4415bf60$0200010a@WT0136> (raw)
In-Reply-To: 14029.1021558521@redhat.com

David Woodhouse wrote:
> Yes. That's what ioremap() does for you. But the map driver will already
be
> setting that up -- just call the map->copy_from function in the chip
probe,
> to read the first 0x40-odd bytes into a buffer, and then print them and
> compare with what you expected to see.

OK, this is what I did:
char buffer[0x40];

map->copy_from(map, (void*)buffer, 0, 0x40);

for (i = 0; i < 0x40; i++)
{
    printk("HKC: map->copy_from copied 0x%x to buffer\n", buffer[i];
}

The result was a continuous stream of 0xf0's. In VxWorks I get
0x1303434953463900 which is "..CIS59.". Does this tell you anything?

HK

  reply	other threads:[~2002-05-16 14:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <001301c1fcd9$76792c40$0200010a@WT0136>
2002-05-15 20:50 ` Trouble indetifying FLASH part Ho-Kuo Chan
2002-05-16 12:33   ` David Woodhouse
     [not found]     ` <5240.1021554647@redhat.com>
2002-05-16 13:36       ` Ho-Kuo Chan
2002-05-16 13:37         ` David Woodhouse
2002-05-16 14:12           ` Ho-Kuo Chan
2002-05-16 14:15             ` David Woodhouse
2002-05-16 14:52               ` Ho-Kuo Chan [this message]
2002-05-16 15:01                 ` David Woodhouse
2002-05-16 17:37                   ` Ho-Kuo Chan
2002-05-23 21:19                   ` Ho-Kuo Chan
2002-05-23 21:44                     ` David Woodhouse
2002-05-24 14:09                       ` Ho-Kuo Chan
2002-05-16  6:53 Jim Zeus
  -- strict thread matches above, loose matches on Subject: below --
2002-05-16 13:25 Ho-Kuo Chan

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='009c01c1fce9$4415bf60$0200010a@WT0136' \
    --to=hchan@wavesat.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.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