Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: Jochen Friedrich <jochen@scram.de>
Cc: linux-tr@linuxtr.net,
	HP900 PARISC mailing list <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] IBM TR patch
Date: Tue, 15 Jan 2002 10:11:58 -0800	[thread overview]
Message-ID: <20020115181158.GT3247@tausq.org> (raw)
In-Reply-To: <Pine.LNX.4.43.0201142041450.7418-200000@alpha.bocc.de>

> this patch fixes some endianess issues of the current ibmtr driver. 
> Although the current uses of htons() etc look correct, they are not: the 
> writew/readw API already do the byte swap on big endian machines.

the write/read macros are defined for pci accesses, and as such take a
LE point of view with respect to memory accesses. I take it that you are
not accessing a PCI device, so that's why you are having problems with
endianess.  I suspect your patch will break the driver on PCI devices...
(assuming there are both PCI and [E]ISA versions of the device that
share the same driver).

> Additionally, i added a switch to turn off IPv4 summing. This might be 
> needed for IPv6 and is absolutely necessary on HP PARISC platform with the 
> current broken ioremap implementation. The IPv4 summing is the only place 
> in the driver that accesses memory directly without the readX or 
> memcpy_fromio macros.

How is ioremap broken? (Just curious). From what I understand ioremap is
currently a nop in the parisc-linux vm/io design.

randolph
-- 
   @..@                                         http://www.TauSq.org/
  (----)
 ( >__< )
 ^^ ~~ ^^

  reply	other threads:[~2002-01-15 18:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-14 19:53 [parisc-linux] IBM TR patch Jochen Friedrich
2002-01-15 18:11 ` Randolph Chung [this message]
2002-01-15 18:18   ` Matthew Wilcox
2002-01-15 19:12     ` Jochen Friedrich
2002-01-15 19:07   ` Jochen Friedrich
2002-01-15 22:10 ` Daniel Engstrom
2002-01-16  1:23   ` Randolph Chung
2002-01-16 20:20   ` Jochen Friedrich
2002-01-19 12:20     ` Daniel Engstrom

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=20020115181158.GT3247@tausq.org \
    --to=randolph@tausq.org \
    --cc=jochen@scram.de \
    --cc=linux-tr@linuxtr.net \
    --cc=parisc-linux@lists.parisc-linux.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