[9fans] Question re source trees

[9fans] Question re source trees

[James A. Robinson]

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

Hi folks,

I notice that http://plan9.bell-labs.com/plan9/download/plan9.iso.bz2
is from 2015-01-10, whereas Richard Miller's
http://plan9.bell-labs.com/sources/contrib/miller/9pi.img.gz

was built on 2016-05-30.  I was wondering whether the changes made
by Mr. Miller for supporting the Raspberry Pi were getting folded
back into a source tree available via means other than those with
an active plan9 system (I see references to  /n/sources/contrib/miller
which I assume is a 9fs mount).

I was specifically curious because I wanted to poke around to get
sense of what kind of support is available for the Raspberry Pi 3
vs. the Raspberry Pi 2.  There were some early emails indicating
a few small changes Mr. Miller needed to make for booting the
system, but I couldn't find anything discussing whether other
hardware was supported (e.g., the built-in wifi on the Pi 3).

Jim

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

Re: [9fans] Question re source trees

[Richard Miller]

> I was wondering whether the changes made
> by Mr. Miller for supporting the Raspberry Pi were getting folded
> back into a source tree available via means other than those with
> an active plan9 system (I see references to  /n/sources/contrib/miller
> which I assume is a 9fs mount).

You can also use a web browser to access /n/sources; it's mapped to
http://plan9.bell-labs.com/sources (when the server isn't down).

Source for all the raspberry pi kernel changes is kept up to date in
http://plan9.bell-labs.com/sources/contrib/miller/9/bcm

> ... I couldn't find anything discussing whether other
> hardware was supported (e.g., the built-in wifi on the Pi 3).

The Broadcom 43430 wifi chip on the pi3 turns out to be functionally
almost the same as the 4330, for which I had written a driver some
time ago for another platform.  The client who commissioned that work
has generously agreed to its release, so 9piwifi support will appear
shortly.  (The driver is working but WPA authentication needs a few
tweaks.)

I can also supply bluetooth code for the pi3 if anyone is interested.

Re: [9fans] Question re source trees

[Kurt H Maier]

On Thu, Sep 29, 2016 at 09:08:27AM +0100, Richard Miller wrote:
>
> I can also supply bluetooth code for the pi3 if anyone is interested.
>

I am interested.  Will it be part of your next pi release?

khm

[9fans] Question re source trees

[Richard Miller]

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

>
> > I can also supply bluetooth code for the pi3 if anyone is interested.
> >
>
> I am interested.  Will it be part of your next pi release?
>
> Probably not for a while. I would have to write some man pages first.

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

Re: [9fans] Question re source trees

[Ole-Hjalmar Kristensen]

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

This is great news. I am thinking of using the Pi3 to control a mobile
platform, and having wifi support without using an external wireless router
would simplify the hardware.

On Thu, Sep 29, 2016 at 10:08 AM, Richard Miller <9fans@hamnavoe.com> wrote:

> > I was wondering whether the changes made
> > by Mr. Miller for supporting the Raspberry Pi were getting folded
> > back into a source tree available via means other than those with
> > an active plan9 system (I see references to  /n/sources/contrib/miller
> > which I assume is a 9fs mount).
>
> You can also use a web browser to access /n/sources; it's mapped to
> http://plan9.bell-labs.com/sources (when the server isn't down).
>
> Source for all the raspberry pi kernel changes is kept up to date in
> http://plan9.bell-labs.com/sources/contrib/miller/9/bcm
>
> > ... I couldn't find anything discussing whether other
> > hardware was supported (e.g., the built-in wifi on the Pi 3).
>
> The Broadcom 43430 wifi chip on the pi3 turns out to be functionally
> almost the same as the 4330, for which I had written a driver some
> time ago for another platform.  The client who commissioned that work
> has generously agreed to its release, so 9piwifi support will appear
> shortly.  (The driver is working but WPA authentication needs a few
> tweaks.)
>
> I can also supply bluetooth code for the pi3 if anyone is interested.
>
>
>

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

Re: [9fans] Question re source trees

[James A. Robinson]

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

​Thank you for the answer, that's very generous of ​you and your client!
(I had thought the http://plan9.bell-labs.com/sources site was having
trouble, looks like maybe it's just Chrome getting aggressive about
HTTPS and failing, I can open the page w/ lynx).


Jim

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

[9fans] plan9.bell-labs.com hates AppleWebKit?

[James A. Robinson]

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

So... Does Alcatel-Lucent have a problem with AppleWebKit
users on principle?

It looks to me as though my problem with browsing around
under http://plan9.bell-labs.com/sources/ (and other subpages)
is because the server doesn't like the User-Agent string:

$ telnet plan9.bell-labs.com 80
Trying 135.104.24.16...
Connected to plan9.bell-labs.com.
Escape character is '^]'.
GET /sources/contrib/ HTTP/1.1
Host: plan9.bell-labs.com
Connection: keep-alive
Cache-Control: max-age=0
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6)
AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36
Accept:
text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
DNT: 1
Accept-Encoding: gzip, deflate, sdch
Accept-Language: en-US,en;q=0.8

HTTP/1.1 200 OK
Connection closed by foreign host.

And here it is again w/o the User-Agent string:

$ telnet plan9.bell-labs.com 80
Trying 135.104.24.16...
Connected to plan9.bell-labs.com.
Escape character is '^]'.
GET /sources/contrib/ HTTP/1.1
Host: plan9.bell-labs.com
Connection: keep-alive
Cache-Control: max-age=0
Upgrade-Insecure-Requests: 1
Accept:
text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
DNT: 1
Accept-Encoding: gzip, deflate, sdch
Accept-Language: en-US,en;q=0.8

HTTP/1.1 200 OK
Server: Plan9
Date: Sun, 02 Oct 2016 17:29:09 GMT
Connection: close
Last-Modified: Fri, 14 Mar 2014 22:14:11 GMT
Content-Type: text/html

[... proper body returned...]

I tried playing around with the UA value and found that if I change
AppleWebKit to something else such as AppleWebKis I get a
response...

Jim

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

Re: [9fans] plan9.bell-labs.com hates AppleWebKit?

[sl]

> So... Does Alcatel-Lucent have a problem with AppleWebKit
> users on principle?

Interesting reversal.

sl

Re: [9fans] plan9.bell-labs.com hates AppleWebKit?

[arisawa]

I can get proper response from http://plan9.bell-labs.com/sources/ by using mac/osx safari.


> 2016/10/03 2:42、James A. Robinson <jimr@highwire.org> のメール：
> 
> So... Does Alcatel-Lucent have a problem with AppleWebKit
> users on principle?
> 
> It looks to me as though my problem with browsing around
> under http://plan9.bell-labs.com/sources/ (and other subpages)
> is because the server doesn't like the User-Agent string:
> 
> $ telnet plan9.bell-labs.com 80
> Trying 135.104.24.16...
> Connected to plan9.bell-labs.com.
> Escape character is '^]'.
> GET /sources/contrib/ HTTP/1.1
> Host: plan9.bell-labs.com
> Connection: keep-alive
> Cache-Control: max-age=0
> Upgrade-Insecure-Requests: 1
> User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36
> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
> DNT: 1
> Accept-Encoding: gzip, deflate, sdch
> Accept-Language: en-US,en;q=0.8
> 
> HTTP/1.1 200 OK
> Connection closed by foreign host.
> 
> And here it is again w/o the User-Agent string:
> 
> $ telnet plan9.bell-labs.com 80
> Trying 135.104.24.16...
> Connected to plan9.bell-labs.com.
> Escape character is '^]'.
> GET /sources/contrib/ HTTP/1.1
> Host: plan9.bell-labs.com
> Connection: keep-alive
> Cache-Control: max-age=0
> Upgrade-Insecure-Requests: 1
> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
> DNT: 1
> Accept-Encoding: gzip, deflate, sdch
> Accept-Language: en-US,en;q=0.8
> 
> HTTP/1.1 200 OK
> Server: Plan9
> Date: Sun, 02 Oct 2016 17:29:09 GMT
> Connection: close
> Last-Modified: Fri, 14 Mar 2014 22:14:11 GMT
> Content-Type: text/html
> 
> [... proper body returned...]
> 
> I tried playing around with the UA value and found that if I change 
> AppleWebKit to something else such as AppleWebKis I get a
> response...
> 
> Jim
> 

Re: [9fans] plan9.bell-labs.com hates AppleWebKit?

[Sergey Zhilkin]

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

Hi all !
Get right response from server, with macOS Sierra beta 10.12.1 (16B2338c)
and Safari 10.0.1 (12602.2.14.0.1)

2016-10-04 15:59 GMT+03:00 arisawa <arisawa@ar.aichi-u.ac.jp>:

> I can get proper response from http://plan9.bell-labs.com/sources/ by
> using mac/osx safari.
>
>
> > 2016/10/03 2:42、James A. Robinson <jimr@highwire.org> のメール：
> >
> > So... Does Alcatel-Lucent have a problem with AppleWebKit
> > users on principle?
> >
> > It looks to me as though my problem with browsing around
> > under http://plan9.bell-labs.com/sources/ (and other subpages)
> > is because the server doesn't like the User-Agent string:
> >
> > $ telnet plan9.bell-labs.com 80
> > Trying 135.104.24.16...
> > Connected to plan9.bell-labs.com.
> > Escape character is '^]'.
> > GET /sources/contrib/ HTTP/1.1
> > Host: plan9.bell-labs.com
> > Connection: keep-alive
> > Cache-Control: max-age=0
> > Upgrade-Insecure-Requests: 1
> > User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6)
> AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36
> > Accept: text/html,application/xhtml+xml,application/xml;q=0.9,
> image/webp,*/*;q=0.8
> > DNT: 1
> > Accept-Encoding: gzip, deflate, sdch
> > Accept-Language: en-US,en;q=0.8
> >
> > HTTP/1.1 200 OK
> > Connection closed by foreign host.
> >
> > And here it is again w/o the User-Agent string:
> >
> > $ telnet plan9.bell-labs.com 80
> > Trying 135.104.24.16...
> > Connected to plan9.bell-labs.com.
> > Escape character is '^]'.
> > GET /sources/contrib/ HTTP/1.1
> > Host: plan9.bell-labs.com
> > Connection: keep-alive
> > Cache-Control: max-age=0
> > Upgrade-Insecure-Requests: 1
> > Accept: text/html,application/xhtml+xml,application/xml;q=0.9,
> image/webp,*/*;q=0.8
> > DNT: 1
> > Accept-Encoding: gzip, deflate, sdch
> > Accept-Language: en-US,en;q=0.8
> >
> > HTTP/1.1 200 OK
> > Server: Plan9
> > Date: Sun, 02 Oct 2016 17:29:09 GMT
> > Connection: close
> > Last-Modified: Fri, 14 Mar 2014 22:14:11 GMT
> > Content-Type: text/html
> >
> > [... proper body returned...]
> >
> > I tried playing around with the UA value and found that if I change
> > AppleWebKit to something else such as AppleWebKis I get a
> > response...
> >
> > Jim
> >
>
>
>


-- 
С наилучшими пожеланиями
Жилкин Сергей
With best regards
Zhilkin Sergey

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

Re: [9fans] Question re source trees

[Kurt H Maier]

On Thu, Sep 29, 2016 at 11:54:03AM +0100, Richard Miller wrote:
>
> > > I can also supply bluetooth code for the pi3 if anyone is interested.
> > >
> >
> > I am interested.  Will it be part of your next pi release?
>
> Probably not for a while. I would have to write some man pages first.

Is your contrib directory on sources the place this code will turn up
when you release it?  Or is there another release mechanism I should be
monitoring?

Thanks,
khm