From: rolf liu <rolfliu@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: ppopov@embeddedalley.com,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
Subject: Re: booting error on db1550 using linux 2.6.12 from linux-mips.org
Date: Thu, 7 Jul 2005 17:27:13 -0700 [thread overview]
Message-ID: <2db32b7205070717271365dd35@mail.gmail.com> (raw)
In-Reply-To: <1120776436.317.57.camel@localhost.localdomain>
I don't have hardware now and will try that option tomorrow. But I
remembered I got the same output before I applied your patch. I wonder
if using the PCI clock as the sole input can help. I read about the
source code provide by HighPoint Technologies. They use
"pci_write_config_byte(dev, 0x5b, 0x21);" instead of
"pci_write_config_byte(dev, 0x5b, 0x23);".
will let you know the result tomorrow.
Thanks
On 7/7/05, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> On Iau, 2005-07-07 at 19:42, rolf liu wrote:
> > Alan,
> > Tried your patch on db1550 and linux 2.6.12. It still doesn't work.
> > During the boot-up, the kernel will hang up right after it prints out:
> >
> > >>hdg: max request size: 128 KiB
>
> > Any suggestion?
>
> Its got started if it gets that far because the LBA48 status has been
> checked. What occurs if you boot with ide=nodma ?
>
>
next prev parent reply other threads:[~2005-07-08 0:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-01 21:17 booting error on db1550 using linux 2.6.12 from linux-mips.org rolf liu
2005-07-01 21:24 ` Pete Popov
2005-07-01 22:35 ` rolf liu
2005-07-01 22:44 ` Pete Popov
2005-07-01 22:52 ` rolf liu
2005-07-05 15:50 ` rolf liu
2005-07-06 7:12 ` Pete Popov
2005-07-06 22:15 ` rolf liu
2005-07-06 22:22 ` Pete Popov
2005-07-07 17:10 ` Alan Cox
2005-07-07 17:19 ` rolf liu
2005-07-07 18:05 ` rolf liu
2005-07-07 18:42 ` rolf liu
2005-07-07 22:47 ` Alan Cox
2005-07-08 0:27 ` rolf liu [this message]
2005-07-08 19:27 ` rolf liu
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=2db32b7205070717271365dd35@mail.gmail.com \
--to=rolfliu@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-mips@linux-mips.org \
--cc=ppopov@embeddedalley.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.