From: Grant Grundler <grundler@cup.hp.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: parisc-linux@puffin.external.hp.com
Subject: Re: [parisc-linux] CVS linux Vs. -test10
Date: Sun, 19 Nov 2000 23:44:42 -0800 [thread overview]
Message-ID: <200011200744.XAA18214@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Sat, 18 Nov 2000 07:24:54 PST." <20001118072454.C30151@parcelfarce.linux.theplanet.co.uk>
Matthew Wilcox wrote:
> On Tue, Nov 14, 2000 at 09:35:01AM -0700, Paul Bame wrote:
> ok, here's my memories.
Thanks Matthew!
hehe...sounds like someone's getting older. :^)
...
> > * drivers/net/eepro100.c: no clue about this one
>
> we were trying to get it to work for the Jan NYLWE show.
I think I did that. IIRC, it's a one-line change to use I/O port
space since MMIO wasn't usable without more invasive changes.
> i doubt we have any changes of note. does anyone have an eepro in an hp?
I have picked nearly 30 i82557/i82558 PCI cards from scrap yard.
And maybe a few i82559 even. Did you need one (or two)? :^)
FWIW, this is the card/driver which I think was causing misaligned
data reference traps. I never had a chance to followup with this though.
At the time, I thought it would be *really* fun to show this working
to HP's marketing team...
> > * fs/nfs/read.c: probably unnecessary hack for broken parisc64 gcc
>
> we certainly don't want to send it upstream, but we don't want to take it
> out until the bug is fixed. is fixing that bug on the webshite todo list?
I don't think so. It's possible it's already fixed.
Relevant CVS log entry:
| revision 1.5
| date: 2000/07/18 03:15:25; author: dhd; state: Exp; lines: +5 -0
| ARGH! When I put in an assertion, NFS stops breaking randomly. I
| suspect this is a compiler or binutils problem but I can't see any
| clear differences in the generated code. I'll debug it later...
This sounds like the hppa64 bug we saw with %r29 getting trashed.
But I don't think David was working on hppa64 kernel at the time.
I can test 32-bit NFS Root tomorrow w/o assertion if no one else
beats me to it.
> > * include/linux/init.h: we use different section names -- why????,
> > probably some unnecessary other differences too
>
> because we use -ffunction-sections. text.init clashes with a function
> called init, and the linker just merges it into the text segment. we
> need it to be separate, so it became init.text. there's patches around
> to do this for other architectures too. just bad naming choices initially.
We need to resolve this in order to merge upstream.
Matthew, any advice on how we should proceed?
Or would be easier for you pester Alan Cox and just get it fixed?
> > * include/linux/wait.h: parisc debugging -- should be removed
>
> yeah, that can die now.
I'd be happy to fix this by clobbering the current version with what's in
linux-2.4.0-test10. But what is the "right" way to revert changes we've made
so this doesn't show up in next merge?
I'll need to know this in order to revert the fs/nfs/read.c change as well.
thanks,
grant
Grant Grundler
Unix Systems Enablement Lab
+1.408.447.7253
next prev parent reply other threads:[~2000-11-20 7:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-14 16:35 [parisc-linux] CVS linux Vs. -test10 Paul Bame
2000-11-18 7:24 ` Matthew Wilcox
2000-11-20 7:44 ` Grant Grundler [this message]
2000-11-20 11:17 ` Matthew Wilcox
2000-11-20 17:34 ` Grant Grundler
2000-11-21 11:34 ` Matthew Wilcox
2000-11-21 21:24 ` Grant Grundler
2000-11-22 0:53 ` Matthew Wilcox
2000-11-22 6:54 ` Ryan Bradetich
2000-11-22 7:18 ` Grant Grundler
2000-11-22 20:11 ` Grant Grundler
2000-11-30 8:09 ` Stephen Zander
2000-11-30 15:44 ` Randolph Chung
2000-11-30 16:16 ` Alan Cox
2000-11-30 16:18 ` Paul Bame
2000-11-20 19:23 ` Grant Grundler
-- strict thread matches above, loose matches on Subject: below --
2000-11-22 6:50 John Marvin
2000-11-22 7:56 ` Grant Grundler
2000-11-22 16:02 ` Paul Bame
2000-11-22 8:11 John Marvin
2000-11-22 19:55 ` Grant Grundler
2000-11-22 20:10 ` Kirk Bresniker
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=200011200744.XAA18214@milano.cup.hp.com \
--to=grundler@cup.hp.com \
--cc=matthew@wil.cx \
--cc=parisc-linux@puffin.external.hp.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