9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] /sys/include/ip.h 5c(1)
Date: Tue,  6 Oct 2009 14:48:44 -0400	[thread overview]
Message-ID: <cec6374fdb0d9adc7baceb227b661fa1@ladd.quanstro.net> (raw)
In-Reply-To: <<13426df10910061136w616f7cf9m2b566606663a9f50@mail.gmail.com>>

> Excuses are eerily the same, each time, almost without regard to the
> product family:
> "nobody else wants that"
> "we no longer release that information"
> etc. etc. etc.

intel has been good to me.  perhaps i'm just
doing different things.

my experience with intel has been that if it's
not available on the web (and the documentation
for most southbridges, intel hd audio, intel gma video,
many wireless chipsets, most intel gbe/10gbe chipsets is),
one can execute an nda and get access.  the guys in
charge of that are great to work with.  and the
amount of stuff available on the web has been increasing
in the last 3 years.

and their documentation is miles better than average.

- erik



       reply	other threads:[~2009-10-06 18:48 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<13426df10910061136w616f7cf9m2b566606663a9f50@mail.gmail.com>
2009-10-06 18:48 ` erik quanstrom [this message]
     [not found] <<4ACED151.8060901@conducive.org>
2009-10-09 15:12 ` erik quanstrom
2009-10-09 18:25   ` lucio
     [not found] <<a17983cabc815054d953faf2696761f2@vitanuova.com>
2009-10-08 22:42 ` erik quanstrom
2009-10-08 23:11   ` Steve Simon
     [not found] <<13426df10910080904l5dc8f3d0sc88ec19f28939a99@mail.gmail.com>
2009-10-08 16:17 ` erik quanstrom
2009-10-08 20:55   ` C H Forsyth
2009-10-09  4:00     ` lucio
2009-10-09  5:59       ` W B Hacker
     [not found] <<18f3fced1ebb90eb9c977b47bbcce424@vitanuova.com>
2009-10-06 22:16 ` erik quanstrom
     [not found] <<13426df10910061021g3b033abbia134769baee934d3@mail.gmail.com>
2009-10-06 18:06 ` erik quanstrom
2009-10-06 18:16   ` ron minnich
     [not found] <<85b966411695929ce06c3edd6e3fd77f@plan9.bell-labs.com>
2009-10-06 16:21 ` erik quanstrom
2009-10-06 16:55   ` geoff
2009-10-06 17:21     ` ron minnich
2009-10-06 18:16       ` W B Hacker
2009-10-06 18:36         ` ron minnich
2009-10-06 18:50           ` W B Hacker
2009-10-06 19:13             ` Lyndon Nerenberg - VE6BBM/VE7TFX
2009-10-06 20:03               ` ron minnich
2009-10-06 20:58                 ` Wes Kussmaul
2009-10-06 21:15       ` Aharon Robbins
2009-10-06 21:32         ` ron minnich
2009-10-07 21:07           ` Aharon Robbins
2009-10-06 21:51         ` C H Forsyth
2009-10-07  0:19           ` Dave Eckhardt
2009-10-07  0:24             ` ron minnich
2009-10-07  1:59               ` W B Hacker
2009-10-08 16:04                 ` ron minnich
2009-10-07  7:59         ` Richard Miller
2009-10-08  7:35           ` Skip Tavakkolian
2009-10-08 10:44             ` Richard Miller
     [not found] <<e7fdc0d20910050644x50fc7ad2hc943a075648fdabd@mail.gmail.com>
2009-10-05 13:50 ` erik quanstrom
2009-10-06  5:44   ` Rodriguez Faszanatas
2009-10-06 16:16     ` geoff
2009-10-06 17:18       ` Steve Simon
2009-10-07  6:24       ` Rodriguez Faszanatas
2009-10-10  1:23         ` Ethan Grammatikidis
     [not found] <<e7fdc0d20910050205l7bfaa624m33a32f7a5269ff9a@mail.gmail.com>
2009-10-05 13:16 ` erik quanstrom
2009-10-05 13:44   ` Rodriguez Faszanatas
2009-10-05  9:05 Rodriguez Faszanatas

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=cec6374fdb0d9adc7baceb227b661fa1@ladd.quanstro.net \
    --to=quanstro@quanstro.net \
    --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).