9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] FQA update
Date: Mon, 03 Apr 2023 15:13:31 -0400	[thread overview]
Message-ID: <99C237A2-984E-43A9-891D-D47FEB2BC241@stanleylieber.com> (raw)
In-Reply-To: <CAPfmpJD_BECzXEqJzoj+7DeCZ2p0hGgiTekW919C+OVgkUjFTA@mail.gmail.com>

On April 3, 2023 2:09:39 PM EDT, adventures in9 <adventuresin9@gmail.com> wrote:
>There is now a kernel for the Mediatek mt7688 in 9Front.  It needs
>drivers for wifi and i2c and such, but it is a start.
>
>I do have a couple other work-in-progress kernels for Arm and Mips.
>https://github.com/adventuresin9?tab=repositories
>
>The Raspberry Pi gets downplayed because it is one of the more
>difficult chips to work with.  Much of the functionality is controlled
>by the GPU, and Broadcom isn't very open about how to work with it.
>Most Arm chips are going to have some kind of compromise because they
>are designed for some particular application.
>
>On Mon, Apr 3, 2023 at 4:54 AM <chris@chrisfroeschl.de> wrote:
>>
>> > I know this is very specific to my needs, but I seldom see much talk of
>> > other micro computers (desktop/server) (especially regarding 9) and would
>> > happily try out some alternatives.
>>
>> Although I know that one doesn't get specific platform support by means of
>> wishing for it.
>>
>> 9front is indeed mainly developed for specific (common) targets. If someone
>> requires more specific hardware to run reliable, he probably has to do some
>> patching himself.
>>
>> I was mainly asking for options/work-in-progress projects I didn't see advertised
>> in the well-known resources. (I doubt there are any)
>>
>> So excuse me for expecting some magic micro controller/computer support out of
>> thin air. I'm just not that educated when it comes to latest hardware products
>> and the like and probably just fell for the easy choice of going with something as
>> common as the pi (which is at least viable on 9front to some degree).
>>
>> The repeated critique of rpi's just got me curious if someone knows something that
>> I don't.
>>
>

damn dude

  reply	other threads:[~2023-04-03 19:15 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-17  5:37 Yury Chumak
2023-03-17 19:52 ` Tobias Heinicke
2023-03-18  3:37 ` sl
2023-03-29  3:32 ` sl
2023-03-29 11:09   ` Yury Chumak
2023-03-31 18:50     ` sl
2023-04-01 20:27       ` Kurt H Maier
2023-04-01 20:52         ` Steve Simon
2023-04-01 21:29           ` ori
2023-04-02  7:10           ` Kurt H Maier
2023-04-02  9:40             ` ooga
2023-04-02 11:29               ` Philip Silva
2023-04-02 14:49                 ` Stanley Lieber
2023-04-02 17:54                   ` Philip Silva
2023-04-02 18:03                     ` Philip Silva
2023-04-02 19:21                       ` hiro
2023-04-06 14:11                         ` cinap_lenrek
2023-04-06 14:19                   ` cinap_lenrek
2023-04-06 16:04                     ` Stanley Lieber
2023-04-02 19:59               ` Kurt H Maier
2023-04-03 10:22         ` chris
2023-04-03 11:50           ` chris
2023-04-03 18:09             ` adventures in9
2023-04-03 19:13               ` Stanley Lieber [this message]
2023-04-03 21:44                 ` sirjofri

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=99C237A2-984E-43A9-891D-D47FEB2BC241@stanleylieber.com \
    --to=sl@stanleylieber.com \
    --cc=9front@9front.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 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).