From: Jacob Todd <jaketodd422@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] etheresis driver
Date: Tue, 4 May 2010 00:29:21 -0400 [thread overview]
Message-ID: <20100504042921.GA20614@zoidberg.hsd1.mi.comcast.net> (raw)
In-Reply-To: <ab6232bab685d7c718d48010f3795374@kw.quanstro.net>
[-- Attachment #1: Type: text/plain, Size: 359 bytes --]
On Mon, May 03, 2010 at 10:16:36PM -0400, erik quanstrom wrote:
> if i had to guess, i'd imagine that the problem is in talking
> to the eeprom. do you have any additional information on
> the chip you have? for example, pci output or
> output from /dev/kmesg on boot? pngs are fine.
http://groups.google.com/group/comp.os.plan9/msg/a74bc8c10f2d5302
[-- Attachment #2: Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2010-05-04 4:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 17:39 Jacob Todd
2010-05-03 18:30 ` erik quanstrom
2010-05-03 21:39 ` Jacob Todd
2010-05-04 2:16 ` erik quanstrom
2010-05-04 4:29 ` Jacob Todd [this message]
2010-05-04 13:48 ` erik quanstrom
2010-05-04 19:46 ` Jacob Todd
2010-05-04 20:03 ` erik quanstrom
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=20100504042921.GA20614@zoidberg.hsd1.mi.comcast.net \
--to=jaketodd422@gmail.com \
--cc=9fans@9fans.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).