public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gabriel Gomiz <gomita@bblanca.com.ar>
To: root@chaos.analogic.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: NCR 7452/3 POS - Retail CMOS NVRAM Driver
Date: Thu, 16 Jan 2003 17:00:24 -0300	[thread overview]
Message-ID: <3E270F58.9020609@bblanca.com.ar> (raw)
In-Reply-To: <Pine.LNX.3.95.1030116080150.3536A-100000@chaos.analogic.com>

Richard B. Johnson wrote:
> On Wed, 15 Jan 2003, Gabriel Gomiz wrote:
>>
>>The memory chips that NCR uses are:
>>1) NEC D43256BGU - NCR POS Model 7452-1011
>>    The chip is 256KB, but NCR says they use only 128KB
>>2) NEC D431000AGW - NCR POS Model 7453-1011
>>    The chip is 1MB, but NCR says they use only 128KB
>>
> 
> Look in the ethernet drivers for the "bit-banging" routines
> used to access NVRAM in the devices. You need to shift bits
> in and out of these devices. They are SERIAL ERPROMS. You
> can get data sheets by using your favorite search engine
> (as I just did).

I grabbed the datasheets of the memory chips and found out the 
following, that changes the incorrect information that I had:

1) NEC D43256BGU is 256Kbits = 32KB (32768 words of 8 bits)

This chip has 15 address lines (A0-A14) and 8 data lines (I/O1 - I/O8).

2) NEC D431000AGW is 1Mbit = 128KB (131072 word of 8 bits)

This chip has 17 address lines (A0-A16) and 8 data lines (I/O1 - I/O8).

So it seems that these chips doesn't have a serial-like interface for 
bit-banging, I am wrong?

-- 
    .^.    Gabriel Gomiz - Red Hat Certified Engineer (RHCE)
    /V\
   // \\
  /(   )\
   ^^-^^   s/Window[$s]/LINUX!!/g or die;


      reply	other threads:[~2003-01-16 19:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-16  0:11 NCR 7452/3 POS - Retail CMOS NVRAM Driver Gabriel Gomiz
2003-01-16 13:06 ` Richard B. Johnson
2003-01-16 20:00   ` Gabriel Gomiz [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=3E270F58.9020609@bblanca.com.ar \
    --to=gomita@bblanca.com.ar \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.com \
    /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