All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Bradetich <rbradetich@uswest.net>
To: jsoe0708@tiscali.be
Cc: grundler@dsl2.external.hp.com,
	Ed Schaller <schallee@darkmist.net>,
	parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] quad tulip now not functional in 2.4.20
Date: 19 Dec 2002 07:27:32 -0700	[thread overview]
Message-ID: <1040308053.24208.4.camel@beavis> (raw)
In-Reply-To: <3DED9A6600002207@ocpmta3.freegates.net>

Joel,

Just a heads up ... I will not even have a chance to look at this for
a week or two.

Thanks,

- Ryan

On Tue, 2002-12-17 at 23:30, jsoe0708@tiscali.be wrote:
> Hi Grant,
> >
> >On Tue, Dec 17, 2002 at 04:14:10PM +0100, jsoe0708@tiscali.be wrote:
> >> >I will try to revert tulip driver and advise you.
> >> Well I find some minutes to do this reverse and it works.
> >> Still have to find the bug ?
> >
> >Unfortunately yes.
> >But since the diff is small, it's alot easier.
> >
> >I'm most suspicious about the added checks for length field in eeprom.
> >But I'll review the diff again and tinker with it today or tomorrow.
> >I added that thinking that code only gets executed when there is no
> >phy table (eg built-in). But the add-on cards do have a phy table.
> >
> (well it seems I do mistake when sent following info)
> [also because diff is small]
> In eeprom.c I also suspect:
> line 193: if (ee_data[27] == 0 || ee_data[ee_data[27]] == 0) {
> 
> which I only reverse into:
> if (ee_data[27] == 0) {
> 
> and it works. Unforunately I do not have enough doc to actulay fix the pb.
> May be Ryan could still help us?
> 
> Joel
> 
> ********************************************************************************
> Controlez mieux votre consommation Internet...surfez Tiscali Complete...http://tiscali.complete.be
> 
> 
> 
> 

  parent reply	other threads:[~2002-12-19 14:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-16  6:45 [parisc-linux] quad tulip now not functional in 2.4.20 Ed Schaller
2002-12-16 23:11 ` Grant Grundler
2002-12-17  7:12   ` jsoe0708
2002-12-18 16:58     ` Grant Grundler
2002-12-18 20:27       ` Ed Schaller
2002-12-19 17:37       ` jsoe0708
2002-12-17 10:43   ` jsoe0708
2002-12-17 15:14     ` jsoe0708
2002-12-17 17:42       ` jsoe0708
2002-12-17 18:19       ` Grant Grundler
2002-12-18  6:30         ` jsoe0708
2002-12-18 17:01           ` Grant Grundler
2002-12-19 14:27           ` Ryan Bradetich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-30 10:59 "Beerse, Corné"
2003-01-30 14:45 ` Michael S.Zick
2003-01-30 15:02   ` Randolph Chung
2003-01-30 15:34     ` Michael S.Zick
2003-01-30 15:38     ` Thibaut VARENE
2003-01-30 15:36       ` Michael S.Zick
2003-01-30 19:23   ` Grant Grundler
2003-02-03  9:40     ` Peter Lavender

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=1040308053.24208.4.camel@beavis \
    --to=rbradetich@uswest.net \
    --cc=grundler@dsl2.external.hp.com \
    --cc=jsoe0708@tiscali.be \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=schallee@darkmist.net \
    /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.