Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@cup.hp.com>
To: Greg Ingram <ingram@symsys.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Booting C100
Date: Mon, 15 Jan 2001 15:50:06 -0800	[thread overview]
Message-ID: <200101152350.PAA10493@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Mon, 15 Jan 2001 13:22:14 PST." <Pine.LNX.4.21.0101151256070.23322-100000@maestro.symsys.com>

Greg Ingram wrote:
> Okay, I grabbed the cross-compiler and various sources and managed to
> build a booting image.  Woohoo!

Good work!

> I also tried the lifimage you just posted
> to the FTP site.  Both kernels died at GSC detection because it didn't
> know the address f5fbf000.  I made this little change to ccio-dma.c:
> 
> --- arch/parisc/kernel/ccio-dma.c.orig  Mon Jan 15 12:40:05 2001
> +++ arch/parisc/kernel/ccio-dma.c       Mon Jan 15 13:05:01 2001
> @@ -1174,6 +1174,7 @@
>  ** that can't be detected by PA/EISA/PCI bus walks.
>  */
>         switch((long) d->hpa) {
> +       case 0xf5fbf000L:       /* C1O0 (wild guess!) */
>         case 0xf7fbf000L:       /* C110 IOA0 LBC (aka GSC port) */
>         case 0xf3fbf000L:       /* C110 IOA0 LBC (aka GSC port) */
>                 /* ccio_hpa same as C200 IOA0 */                             

As Ryan noted, this is a hack. We need a real PA bus walk - not
just depending on the devices PDC tells us about.
     

> Data access rights fault in kernel: Code=26 regs=c7f9c840 (Addr=0000000c)

Looks like a null ptr dereference.

>      YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
> PSW: 00000000000001100000000000001011
> r0-3     00000000 c02b2580 c018e784 c02c2c88
...
> IASQ: 00000000 00000000 IAOQ: c010c8fc c010c900

IOAQ is the current PC
GR02 is the return ptr - ie caller address + 8

See build-tools/a.c
If you look up the symbols of those, very likely you'll
find the code that doesn't like your C100.

grant

Grant Grundler
Unix Systems Enablement Lab
+1.408.447.7253

  parent reply	other threads:[~2001-01-15 23:44 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-12  2:37 [parisc-linux] 715/80 problem Phillip D. Beal
2001-01-12  4:40 ` Alex deVries
2001-01-12 10:20   ` Andrew Shugg
2001-01-14  3:35     ` Phillip D. Beal
2001-01-14  6:04       ` Alex deVries
2001-01-14 18:02         ` Phillip D. Beal
2001-01-14 18:42           ` Alex deVries
2001-01-14 20:13             ` Matthew Wilcox
2001-01-15 14:51               ` Phillip D. Beal
2001-01-15  0:03             ` Grant Grundler
2001-01-15 16:44               ` [parisc-linux] Booting C100 Greg Ingram
2001-01-15 17:29                 ` Grant Grundler
2001-01-15 17:57                   ` Greg Ingram
2001-01-15 18:58                     ` Grant Grundler
2001-01-15 19:22                     ` Greg Ingram
2001-01-15 19:57                       ` Ryan Bradetich
2001-01-15 23:50                       ` Grant Grundler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-01-15 21:30 Aleksandr Konstantinov
2001-01-15 22:17 ` Matthew Wilcox
2001-01-16 13:56   ` Aleksandr Konstantinov
2001-01-16 15:22     ` Matthew Wilcox
2001-01-16 17:46     ` Helge Deller
2001-01-17  4:40       ` Aleksandr Konstantinov
2001-01-17 20:55 Phillip D. Beal

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=200101152350.PAA10493@milano.cup.hp.com \
    --to=grundler@cup.hp.com \
    --cc=ingram@symsys.com \
    --cc=parisc-linux@thepuffingroup.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