i believe that this works for vga attached monitors, vesa says that when the
clocks
disappear on the sync the monitor should shutdown.
the raspberry pi uses hdmi and also it doesn't use a vesa bios, it has a gpu
bios
which does a similar job but is not standardised, and, though it is documented,
Yeah, I was kind of the mentality of "Well, if its HDMi, its basically
single link DVI..." Of course, it is its own standard, CEC is probably the
simplest way of achieving this, there is a CEC-serial bridge, various
websites have them. I've looked into them before, before I started using
all Macs b
On Fri May 16 04:47:03 EDT 2014, st...@quintile.net wrote:
> i believe that this works for vga attached monitors, vesa says that when the
> clocks
> disappear on the sync the monitor should shutdown.
>
> the raspberry pi uses hdmi and also it doesn't use a vesa bios, it has a gpu
> bios
> which
Mmm, that feels like good and bad news.
I know richard did what he could to shut down the screen when
its idle for a while so that seems to do the right thing with vga
monitors, but I guess I do need CEC.
Oh well, time for more digging.
-Steve
On Fri May 16 08:33:41 EDT 2014, st...@quintile.net wrote:
> Mmm, that feels like good and bad news.
>
> I know richard did what he could to shut down the screen when
> its idle for a while so that seems to do the right thing with vga
> monitors, but I guess I do need CEC.
>
> Oh well, time for m
> On May 16, 2014, at 5:43 AM, erik quanstrom wrote:
>
>> On Fri May 16 08:33:41 EDT 2014, st...@quintile.net wrote:
>> Mmm, that feels like good and bad news.
>>
>> I know richard did what he could to shut down the screen when
>> its idle for a while so that seems to do the right thing with vg
btw, whats the program that gets hit by alarm notes but wants to
continue with Bread()?
--
cinap
On Fri May 16 15:26:28 EDT 2014, cinap_len...@felloff.net wrote:
> btw, whats the program that gets hit by alarm notes but wants to
> continue with Bread()?
there's one you wrote, but more on that offline.
- erik
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
just did a mk in /sys/src/9/bcm and it builds just fine.
what is "/sys/src/9/9-bcm"?
--
cinap
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 wrote:
> So I ran across this ( https://github.com/elewarr/plan9-bcm ) awhile back
> and decided it would be fun to try to stic
Ok, it ran when bound to /sys/src/9/bcm. Flawless success. @cinap_lenrek,
the folder was the source for the bcm kernel thing I linked above, it's
built to support GPIO afaik, I'd like to play with GPIO whilst I learn
plan9 on this pi.
If I may ask, what is the reason that it ran when bound to bcm,
12 matches
Mail list logo