From: Pete Popov <ppopov@pacbell.net>
To: Wayne Gowcher <wgowcher@yahoo.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: USB OHCI on 2.4.2 kernel using r4k processor
Date: Tue, 10 Jul 2001 21:36:36 -0700 [thread overview]
Message-ID: <3B4BD7D4.1060003@pacbell.net> (raw)
In-Reply-To: 20010710194526.44019.qmail@web11906.mail.yahoo.com
Wayne Gowcher wrote:
> Dear All,
>
> Has anyone got USB OHCI running on a 2.4.2 kernel with
> a mips r4k processor ?
Yes, on a couple of different boards.
> I have successfully used the above with a r3k mips
> processor but now after porting the same base code to
> a r4k processor the kernel throws an OOPS.
>
> I believe the problem may lay with the writeback cache
> because when I disable the d cache on the r4k 2.4.2
> kernel USB works fine !
> I did some digging around and noted that the working
> aic7xxx driver I have on the 2.4.2 r4k makes use of
> pci_map_single to handle cache flushing ( ??? please
> correct me if I am wrong ) and that this type of code
> doesn't make it into the usb code until 2.4.4 of the
> sgi linux kernel.
> Does anyone have a "back patch" to apply to the 2.4.2
> usb code ?
> If not I am thinking of attempting this myself and
> would welcome any comments / advice about doing this
Steve at MontaVista did the usb work for mips about six months ago on an
ITE 8172 board. Since then we've also ported it to the Alchemy Au1000
board, both running on 2.4.2. He forwarded all patches to the usb
maintainer but it looks like it took a bit of time for all the patches
to be applied. I don't know if we still have patches against the 2.4.2
tree. One thing you can do is next Monday check our ftp site (HHL2.0
for mips should be released by early next week), grab the generic HHL2.0
mips kernel, and diff all the usb code against the stock 2.4.2. I don't
think it would be too bad of a job.
Pete
next prev parent reply other threads:[~2001-07-11 4:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-01 21:05 Linux on PlayStation 2 Jun Sun
2001-06-01 21:35 ` Mark Lehrer
2001-06-01 22:06 ` Wayne Gowcher
2001-06-04 17:48 ` Native compile on the target using RedHat 6.1 rpms Wayne Gowcher
2001-06-04 19:20 ` Native compile on the target using RedHat 6.1 rpms - Update Wayne Gowcher
2001-06-04 20:36 ` Ralf Baechle
2001-06-04 20:53 ` Wayne Gowcher
2001-06-04 21:54 ` Ralf Baechle
2001-06-05 7:50 ` Houten K.H.C. van (Karel)
2001-07-10 19:45 ` USB OHCI on 2.4.2 kernel using r4k processor Wayne Gowcher
2001-07-11 4:36 ` Pete Popov [this message]
2001-06-04 20:28 ` Native compile on the target using RedHat 6.1 rpms Ralf Baechle
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=3B4BD7D4.1060003@pacbell.net \
--to=ppopov@pacbell.net \
--cc=linux-mips@oss.sgi.com \
--cc=wgowcher@yahoo.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