9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] plan9-bcm GPIO control raspberry pi
Date: Fri, 16 May 2014 13:46:25 -0700	[thread overview]
Message-ID: <CAJSxfmKUHUQCHib3W+94x7Nyq881dQeGUcjccX+n9v32Dtw90Q@mail.gmail.com> (raw)
In-Reply-To: <CADmmOS9O_m-xy_ij8x5dj_-3+VJpTbYJKGWmkObq=dn884_KgA@mail.gmail.com>

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

i'm guessing that plan9-bcm source directory should be bound -- bind(1) --
to /sys/src/9/9-bcm (or even /sys/src/9/bcm).



On Fri, May 16, 2014 at 1:33 PM, Sean Hinchee <henesy.dev@gmail.com> wrote:

> So I ran across this ( https://github.com/elewarr/plan9-bcm ) awhile back
> and decided it would be fun to try to stick it on my pi running 9front.
> Problem is I'm either too new to this, or am missing something really basic
> when I'm trying to compile the kernel. Normally iirc one just has to run
> "mk install" and things tend to come together, but I'm getting an error "No
> recipe to make 'fpi.5' in director /sys/src/9/9-bcm"
>
> I realize that the 5 corresponds to the ARM arch and I assume it is
> supposed to be made automatically, I'm not sure if tehre's some
> documentation somewhere on this I missed or if I should just dig through
> the source to find out what it is/should be.
>
> Thoughts?
>
>
>

[-- Attachment #2: Type: text/html, Size: 1412 bytes --]

  parent reply	other threads:[~2014-05-16 20:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-16 20:33 Sean Hinchee
2014-05-16 20:40 ` cinap_lenrek
2014-05-16 20:46 ` Skip Tavakkolian [this message]
2014-05-17  3:12   ` Sean Hinchee

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=CAJSxfmKUHUQCHib3W+94x7Nyq881dQeGUcjccX+n9v32Dtw90Q@mail.gmail.com \
    --to=skip.tavakkolian@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).