9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: hiro <23hiro@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] More about /dev/draw
Date: Sun, 29 May 2016 10:05:19 +0200	[thread overview]
Message-ID: <CAFSF3XMU6cGcSJA4U9QXPxgh8wtxRNZzAAkP3Q1HKbD6af3_YQ@mail.gmail.com> (raw)
In-Reply-To: <c1b5ea7757945456e4faf3b3f4ce6365@SDF.ORG>

jfmxl, this mailing list is not a hardware store. how are we supposed
to know what "digital plug-in" means?
if you still have the package of your TV or the manual it might give a
hint. Otherwise I'm sure you know how to google.

On 5/29/16, jfmxl <jfmxl@sdf.org> wrote:
> Actually, looking at the back of the monitor, it has an analog vga
> plug-in and a similar sized digital plug-in, but no HDMI. Can I still
> use it with Raspberry Pi Plan 9?
>
> On 2016-05-29 12:59, jfmxl wrote:
>> Thanks for the answer, Steve.
>>
>> Do you suppose Pi 3 may have fixed the 'sub driver' bugs? What's a
>> 'sub driver'? not 'usb driver', or is it? The audio out is broken, but
>> it's your fault? How is that?
>>
>> On 2016-05-29 12:50, Steve Simon wrote:
>>> I use the Pi 2 version daily at work with an hdmi monitor.
>>>
>>> there seem to be a couple of lurking bugs in the sub driver which
>>> generate spurious grumbles and seem to prevent sub serial adapters
>>> from working, which is a minor annoyance. Other than that it works
>>> like a charm.
>>>
>>> audio out is still broken too which is a continuous source of guilt to
>>> me -
>>> I will fix that one day.
>>>
>>> -Steve
>>>
>>>
>>>> On 29 May 2016, at 06:40, jfmxl <jfmxl@SDF.ORG> wrote:
>>>>
>>>> I see an image at bell labs for the raspberry pi.
>>>> http://plan9.bell-labs.com/sources/contrib/miller/9pi.img.gz
>>>>
>>>> I see that there are Raspberry Pi 2 Model Bs and Raspberry Pi 3 Model
>>>> Bs for sale. Will either one work with that image?
>>>>
>>>> I have a Samsung SyncMaster E1920 I could use, it's got an 'HDMI'
>>>> connection, I believe. Am I good to go?
>>>>
>>>>
>>>>
>>>>> On 2016-05-29 00:34, Skip Tavakkolian wrote:
>>>>> a quick and easy way to get a local Plan 9 terminal is to use 9Pi
>>>>> (Plan 9 on Raspberry Pi). with Go 1.6 and later you can cross
>>>>> compile
>>>>> for plan9/arm.
>>>>> On Sat, May 28, 2016 at 10:24 AM Dave MacFarlane <driusan@gmail.com>
>>>>> wrote:
>>>>>> Either I'm going insane, the default Plan 9 /dev/draw in-memory
>>>>>> implementation
>>>>>> doesn't implement draw(3), or possibly both.
>>>>>> When I do the following, it works as expected under both drawterm
>>>>>> and a locally mounted instance:
>>>>>> 1. Allocate a screen with an 'A' message
>>>>>> 2. Allocate an image on the screen of the same size as /dev/wctl
>>>>>> with a 'b' message
>>>>>> 3. Draw the image over the window with a 'd' message
>>>>>> 4. Flush the buffer with 'v'
>>>>>> When I do the following, it works under drawterm, but not with a
>>>>>> local /dev/draw implementation:
>>>>>> Steps 1-2 above
>>>>>> 3. Allocate another image of some arbitrary fill colour with 'b'
>>>>>> (with or without the repl bit)
>>>>>> 4a. (Optional, doesn't seem to make a difference) set the
>>>>>> compositing operator with 'O'
>>>>>> 4b. Draw the new image over a portion of the window image from step
>>>>>> 2 with 'd'
>>>>>> 5. Go to step 3-4 from the first variation.
>>>>>> (I don't have a 9front instance to test on.)
>>>>>> On the other hand, replacing a portion of the image from step 2
>>>>>> with
>>>>>> 'y' works under either. (I haven't gotten around to using 'Y' when
>>>>>> appropriate yet.)
>>>>>> Basically, I can only get any variation of this code:
>>>>> https://github.com/driusan/exp/blob/18a78a1549541d46d26cb6088a904585c386d812/shiny/driver/devdrawdriver/uploadimpl.go#L50
>>>>>> to work under drawterm.
>>>>>> The end result is that under a local Plan 9 instance the basic
>>>>>> sample shiny test looks like this:
>>>>>> http://driusan.github.io/plan9/basicmem.png
>>>>>> Instead of this:
>>>>>> http://driusan.github.io/plan9/basicdrawterm.png
>>>>>> Does anyone have any pointers? I don't have much access to a
>>>>>> physical Plan 9 machine, so I'm having trouble debugging this since
>>>>>> it works under drawterm (or perhaps is buggy under drawterm in a
>>>>>> way
>>>>>> that makes it seem like it's working..)
>>>>>> It would also potentially be helpful if someone who uses Go under
>>>>>> 9front could let me know how x/exp/shiny/examples/basic looks with
>>>>>> the shiny driver in that branch, but I'm not sure that it matters
>>>>>> since it'll most likely be the same as one of the above..
>>>>>> - Dave
>>>>
>
>
>



  reply	other threads:[~2016-05-29  8:05 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-28 17:23 Dave MacFarlane
2016-05-28 17:34 ` Skip Tavakkolian
2016-05-28 17:49   ` Dave MacFarlane
2016-05-28 18:04     ` hiro
2016-05-28 18:28     ` Steve Simon
2016-05-29  5:40   ` jfmxl
2016-05-29  5:50     ` Steve Simon
2016-05-29  5:59       ` jfmxl
2016-05-29  6:19         ` jfmxl
2016-05-29  8:05           ` hiro [this message]
2016-05-29 17:25           ` trebol55555
2016-05-31  8:41       ` Richard Miller
2016-05-31  8:14     ` Richard Miller
2016-05-31 14:18       ` jfmxl
2016-05-29 10:50 ` Charles Forsyth
2016-05-29 12:44   ` Dave MacFarlane
2016-05-29 12:58     ` Charles Forsyth
2016-05-30  0:30       ` Dave MacFarlane
2016-05-30  9:20         ` Richard Miller
2016-05-30  9:27           ` cinap_lenrek
2016-05-30 13:11             ` Dave MacFarlane
2016-05-30 10:08           ` Richard Miller
2016-05-30 12:37             ` Richard Miller
2016-05-30 13:13               ` Dave MacFarlane
2016-05-30 13:53                 ` Richard Miller
     [not found] <1927218855.974253.1464549855538.JavaMail.yahoo.ref@mail.yahoo.com>
2016-05-29 19:24 ` Brian L. Stuart
2016-05-29 22:47   ` jfmxl

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=CAFSF3XMU6cGcSJA4U9QXPxgh8wtxRNZzAAkP3Q1HKbD6af3_YQ@mail.gmail.com \
    --to=23hiro@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).