Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Marco Braga" <marco.braga@gmail.com>
To: linux-mips@linux-mips.org
Subject: Re: Linux kernel 2.6.20, PCI and hpt266
Date: Mon, 5 Mar 2007 14:57:12 +0100	[thread overview]
Message-ID: <d459bb380703050557o4dea6fs5fa3b336d37b9f@mail.gmail.com> (raw)
In-Reply-To: <45EC101D.8050600@ru.mvista.com>

[-- Attachment #1: Type: text/plain, Size: 1854 bytes --]

2007/3/5, Sergei Shtylyov <sshtylyov@ru.mvista.com>:

> Hello, I am trying to run kernel 2.6.20 on an Au1500 based board. Versions
> > 2.4.x of the kernel are correctly working.
>
>     How could they work I wonder? :-O


Eheheh :-)


> > Problem: on the board there is a HighPoint 371N ATA controller. At the
>
>     There's *no* proper support for HPT371N in 2.4.x.


We've modified them to work. We fixed the "first channel disabled" problem
and the "set pll with a wrong algorithm", etc. :-)


> Details:
> > The driver I use is "drivers/ide/pci/hpt266.c". I've already fixed the
>
>     I guess you mean hpt366.c. :-)


Whoops. Right. I'm using hpt366.c. I'd also like to try the nel libata
drivers.


> > timing problems and PLL configuration that afflict this controller, and
> > removed RESOURCE_64BIT to fix problems with the PCI bus on mips and
> > resource_size_t casts.
>
>     Erm, does it indeed fix the problem I wonder?


Well, at least this change removed the "skipping PCI config due to resource
conflict" error.


>     The PCI config. space accesses use completely different meachanism
> form
> I/O and memory accesses.


I suspected this, but sadly I am novice to PCI. Thank you very much, Sergei.

Today I've done another test: dumping I/O ATA registers, and the results are
puzzling:

The format is:

[hw->io_ports index] [I/O port addr] [I/O port value]

[17179571.588000] 0 addr: 0x1408  val: 0x08
[17179571.596000] 1 addr: 0x1409  val: 0x09
[17179571.608000] 2 addr: 0x140a  val: 0x0a
[17179571.620000] 3 addr: 0x140b  val: 0x0b
[17179571.632000] 4 addr: 0x140c  val: 0x0c
[17179571.644000] 5 addr: 0x140d  val: 0x0d
[17179571.656000] 6 addr: 0x140e  val: 0xa0
[17179571.668000] 7 addr: 0x140f  val: 0x0f
[17179571.680000] 8 addr: 0x1416  val: 0x0a
[17179571.692000] 9 addr: 0x00  val: 0x48

The values seem wrong to me..

Bye!

[-- Attachment #2: Type: text/html, Size: 3257 bytes --]

  reply	other threads:[~2007-03-05 13:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-04 12:27 Linux kernel 2.6.20, PCI and hpt266 Marco Braga
2007-03-05 12:42 ` Sergei Shtylyov
2007-03-05 13:57   ` Marco Braga [this message]
2007-03-06  8:16   ` Marco Braga
2007-03-12  7:33   ` Marco Braga

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=d459bb380703050557o4dea6fs5fa3b336d37b9f@mail.gmail.com \
    --to=marco.braga@gmail.com \
    --cc=linux-mips@linux-mips.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