9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio De Re <lucio.dere@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Someone made a Wayland compositor based on Rio, Wio
Date: Sun,  5 May 2019 17:32:03 +0200	[thread overview]
Message-ID: <CAJQ9t7jcp7MVowbgovdbUx5fdHJb6mmmjML7PsieS9fJ4BiLPg@mail.gmail.com> (raw)
In-Reply-To: <95BF661A6D9D8659CE1189D216FE6706@felloff.net>

On 5/5/19, cinap_lenrek@felloff.net <cinap_lenrek@felloff.net> wrote:
> type !rc at the bootargs prompt to get a shell, then run:
>
> grep '^02' '#$/pci/'*ctl
>
> which prints the pci information for all network cards. that
> should get us closer to why the probing code fails.
>
I've been using a handful of those adapters for a long time, the
legacy etherelnk3.c for i386 works flawlessly with them.

I'd rather redirect the effort to document the ethernet adapters that
have been proven to work.  Down here, the challenge isn't antiquated
adapters, it is bad quality ones, that are cheap, but even Linux,
sometimes Windows doesn't support them. And it's all you get.

What I'm suggesting is that we keep the supported hardware list up to
date and provide some details of where it can or could be sourced. It
would certainly make my life a lot simpler (so would moving back to
Europe, but that's a bit less achievable).

That said, I'll see what I can do about the PCI details. I'll probably
have to copy them manually.

Lucio.



  reply	other threads:[~2019-05-05 15:32 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-05 15:22 cinap_lenrek
2019-05-05 15:32 ` Lucio De Re [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-05-07  5:40 cinap_lenrek
2019-05-07 14:15 ` Lucio De Re
2019-05-05 15:11 cinap_lenrek
2019-05-05 14:14 cinap_lenrek
2019-05-05 15:59 ` Jens Staal
2019-05-05 12:32 cinap_lenrek
2019-05-05 13:50 ` Jens Staal
2019-05-05 17:16   ` hiro
2019-05-05 13:53 ` Lucio De Re
2019-05-05 15:14 ` Lucio De Re
2019-05-07  4:15 ` Lucio De Re
2019-05-08 12:32   ` Ethan Gardener
2019-05-09  7:39     ` Lucio De Re
2019-05-09  9:37       ` hiro
2019-05-04 22:53 umbraticus
2019-05-04 22:47 umbraticus
2019-05-05  7:53 ` hiro
2019-05-05  9:33   ` Lucio De Re
2019-05-05 10:01     ` hiro
2019-05-05 10:15       ` Lucio De Re
2019-05-05 11:09         ` hiro
2019-05-02  4:12 Ryan Gonzalez
2019-05-02  4:17 ` Rodrigo G. López
2019-05-02  4:36 ` Skip Tavakkolian
2019-05-02  4:56   ` David Arnold
2019-05-02  7:13   ` Fazlul Shahriar
2019-05-02 11:15     ` hiro
2019-05-02 11:10   ` hiro
2019-05-02 14:07     ` hiro
2019-05-03  0:47     ` Skip Tavakkolian
2019-05-03  1:27       ` Dan Cross
2019-05-03  7:59         ` hiro
2019-05-03  8:20           ` hiro
2019-05-03 11:52             ` Lucio De Re
2019-05-03 12:32               ` hiro
2019-05-03 12:35                 ` hiro
2019-05-03 17:01                 ` Lucio De Re
2019-05-04 20:53                   ` hiro
2019-05-05  3:19                     ` Lucio De Re
2019-05-05  7:51                       ` hiro
2019-05-05  8:34                         ` Lucio De Re
2019-05-03 23:08                 ` Ethan Gardener
2019-05-04  5:55                   ` Jens Staal
2019-05-04  7:04                     ` hiro
2019-05-07  3:48       ` 岡本健二
2019-05-03  2:06     ` Bakul Shah

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=CAJQ9t7jcp7MVowbgovdbUx5fdHJb6mmmjML7PsieS9fJ4BiLPg@mail.gmail.com \
    --to=lucio.dere@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).