From: Gabriel Paubert <paubert@iram.es>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH 2/8] Add uli1575 pci-bridge sector to MPC8641HPCN dts file.
Date: Sun, 3 Jun 2007 20:20:21 +0200 [thread overview]
Message-ID: <20070603182020.GA10355@iram.es> (raw)
In-Reply-To: <3ffee021f3b721bde0253b1310d4958a@kernel.crashing.org>
On Sun, Jun 03, 2007 at 04:42:38PM +0200, Segher Boessenkool wrote:
> >>This is an IBM NVRAM thing -- write address to ISA I/O
> >>0x74/0x75, read/write a byte from 0x76.
> >
> >Data is 0x77 actually. Port 0x76 systematically returns 0xff
> >on this board (I have one at hand right now and am doing
> >accesses with the firmware).
>
> Oh okay, I don't know exactly what chip this is so
> obviously my information isn't 100% ;-)
>
> >>>ISA Device, Slot 0, LogicalDev 0: PNP0B00, SystemPeripheral,
> >>>RealTimeClock, #-1, interface 129
> >>> Device flags 2800: Integrated, Static
> >>> Packets describing allocated resources:
> >>> Variable (16 decoded bits) I/O port
> >>> from 0x0074 to 0x0074, alignment 1, 2 ports
> >>> Variable (16 decoded bits) I/O port
> >>> from 0x0077 to 0x0077, alignment 1, 1 ports
> >>> Chip identification: MOT3040
> >>> Small vendor item type 0x00, data (hex): 01 f8 1f 00 00
> >>
> >>The I/O port numbers here are wrong.
> >
> >No they aren't. It uses exactly the same port as for the NVRAM.
>
> Then its claim to be PNP 0b00 is incorrect.
>
> >Otherwise the "feature" of this RTC is that its interrupt
> >is not connected.
>
> Dunno what you mean here?
On a standard PC, the RTC is connected to interrupt
8 of the 8259 pair. On these boards the interrupt output
of the RTC is not connected (there is no interrupt
in the list of properties). Interrupt 8 is connected
to a front panel button labeled "ABT".
>
> >>rtc@i70 {
> >> device_type = "rtc";
> >> reg = <1 70 2>;
> >> compatible = "pnpPNP,b00";
> >>}
> >>
> >
> >Nope, there is nothing at 0x70-0x71 (read returns 0xff). The chip
> >is a 48T59.
>
> [Not so easy to find a datasheet for that -- STM M48T59Y
> is what I found in the end]
It is the correct one.
>
> This chip doesn't sit on any I/O port range, it is 8kB
> of direct-mapped standard SRAM stuff. There must be
> some latches or such on your board, or perhaps this is
> driven via some superio chip or something like that.
Indeed, the latches are a bit hard to find (they are inside a
Lattice chip), and the data byte is directly connected to the
ISA bus of the PIB (W83C553 / W53C554).
On some variants of the board, there is not even a superIO chip
(only a discrete UART, TL16C550 or similar).
>
> >Actually I wonder
> >whether using PNP0B00 is correct in the residual data here.
>
> It's not correct at all, no.
Ok. I don't know well the PNP spec. I don't really remember
also what the chip identification means in the residual data,
but it is always MOT3040. OTOH, there is a but in more
recent versions, that claims that the NVRAM data size is
32768 and not 8192...
>
> Not sure how best to describe this thing -- one master
> node with a kid for both nvram and rtc; one node; or
> perhaps one node for rtc, with a child node for nvram.
>
Hey, at least you now understand why I was asking the question :-)
This is the only device on these boards that really causes
me trouble, for all the others I think I can get a reasonable
description in the device tree.
Gabriel
next prev parent reply other threads:[~2007-06-03 18:20 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 17:48 [PATCH 2/8] Add uli1575 pci-bridge sector to MPC8641HPCN dts file Jon Loeliger
2007-06-01 18:58 ` Segher Boessenkool
2007-06-01 21:45 ` Wade Farnsworth
2007-06-02 8:22 ` Segher Boessenkool
2007-06-02 8:53 ` Gabriel Paubert
2007-06-02 9:01 ` Segher Boessenkool
2007-06-02 19:53 ` Gabriel Paubert
2007-06-02 20:23 ` Segher Boessenkool
2007-06-03 0:01 ` Benjamin Herrenschmidt
2007-06-03 7:41 ` Segher Boessenkool
2007-06-03 8:33 ` Gabriel Paubert
2007-06-03 8:57 ` Segher Boessenkool
2007-06-03 9:12 ` Benjamin Herrenschmidt
2007-06-03 10:02 ` Segher Boessenkool
2007-06-03 10:10 ` Gabriel Paubert
2007-06-03 11:42 ` Segher Boessenkool
2007-06-03 12:43 ` Gabriel Paubert
2007-06-03 14:42 ` Segher Boessenkool
2007-06-03 18:20 ` Gabriel Paubert [this message]
2007-06-03 18:56 ` Segher Boessenkool
2007-06-03 9:07 ` Benjamin Herrenschmidt
2007-06-03 9:59 ` Segher Boessenkool
2007-06-03 14:50 ` Jon Loeliger
2007-06-03 17:27 ` Segher Boessenkool
2007-06-04 20:27 ` Andy Fleming
2007-06-04 22:31 ` Randy Vinson
2007-06-05 19:16 ` Andy Fleming
2007-06-05 20:28 ` Randy Vinson
2007-06-06 7:09 ` Benjamin Herrenschmidt
2007-06-07 16:21 ` Andy Fleming
2007-06-07 16:53 ` Segher Boessenkool
2007-06-07 22:12 ` Benjamin Herrenschmidt
2007-06-08 8:29 ` Segher Boessenkool
2007-06-08 8:32 ` Benjamin Herrenschmidt
2007-06-05 6:05 ` Zang Roy-r61911
2007-06-02 23:52 ` Benjamin Herrenschmidt
2007-06-02 23:51 ` Benjamin Herrenschmidt
2007-06-03 8:59 ` Geert Uytterhoeven
2007-06-04 18:50 ` Jon Loeliger
2007-06-04 19:27 ` Segher Boessenkool
2007-06-01 23:28 ` Benjamin Herrenschmidt
2007-06-01 23:36 ` Jon Loeliger
2007-06-02 0:22 ` Benjamin Herrenschmidt
2007-06-02 8:28 ` Segher Boessenkool
2007-06-02 16:04 ` Jon Loeliger
2007-06-02 20:00 ` Segher Boessenkool
2007-06-02 23:16 ` Benjamin Herrenschmidt
2007-06-03 7:37 ` Segher Boessenkool
2007-06-04 0:16 ` Olof Johansson
2007-06-04 8:18 ` Segher Boessenkool
2007-06-02 8:25 ` Segher Boessenkool
2007-06-02 23:50 ` Benjamin Herrenschmidt
2007-06-03 0:13 ` Gabriel Paubert
2007-06-03 7:42 ` Segher Boessenkool
2007-06-03 7:53 ` Gabriel Paubert
2007-06-04 18:49 ` Jon Loeliger
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=20070603182020.GA10355@iram.es \
--to=paubert@iram.es \
--cc=linuxppc-dev@ozlabs.org \
--cc=segher@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).