All of lore.kernel.org
 help / color / mirror / Atom feed
From: "christophe barbé" <christophe.barbe.ml@online.fr>
To: lkml <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@zip.com.au>
Subject: vortex eeprom
Date: Mon, 8 Apr 2002 11:12:39 -0400	[thread overview]
Message-ID: <20020408151238.GD7174@localhost> (raw)

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

I am trying to understand the vortex driver.
I believe that I am not looking at the correct documentation.

I read The following doc :

PCI/EISA Bus-Master Adaptater Driver Technical Reference
Members of the 3Com EtherLink III and Fast Etherlink families of adapters
Manual Part Number 09-0681-001B

The reason I believe there is a better doc is that the driver read info1
and info2 fields from the EEPROM and then does :

 if (vp->info1 & 0x8000) {
    vp->full_duplex = 1;
    if (print_info)
       printk(KERN_INFO "Full duplex capable\n");
 }       

 ...

 if (print_info) {
    printk(KERN_INFO "  Enabling bus-master transmits and %s receives.\n",
          (vp->info2 & 1) ? "early" : "whole-frame" );
 }

But in my doc both these bits are marked 'reserved'.

I understand that these bits could be defined in more recent chipset but
in the doc I am looking at the full duplex capability is defined in
another field in the EEPROM:

   Capabilities Word (offset 0x10) : supportsFullDuplex bit (bit 1)

Christophe

-- 
Christophe Barbé <christophe.barbe@ufies.org>
GnuPG FingerPrint: E0F6 FADF 2A5C F072 6AF8  F67A 8F45 2F1E D72C B41E

Ce que l'on conçoit bien s'énonce clairement,
Et les mots pour le dire arrivent aisément.
   Nicolas Boileau, L'Art poétique

[-- Attachment #2: Type: application/pgp-signature, Size: 241 bytes --]

                 reply	other threads:[~2002-04-08 15:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20020408151238.GD7174@localhost \
    --to=christophe.barbe.ml@online.fr \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.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 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.