9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Sheevaplug - USB working? Just checking
Date: Mon,  6 Sep 2010 22:32:54 +0100	[thread overview]
Message-ID: <06D07BCD-9C82-4757-9C2C-25DC21256FD7@fastmail.fm> (raw)
In-Reply-To: <5d0a241d62b311d331506cf050aa9342@9netics.com>


On 6 Sep 2010, at 6:55 pm, Skip Tavakkolian wrote:

> it works for all usb disks i've tried but has never worked for
> Bluetooth devices.

well if it works for all usb disks it's worth my while getting one,  
not a sheevaplug as such, rather a seagate freeagent go dockstar  
which is currently €25 from atelco.de or $40 direct from seagate.  
aiju tells me it has the same soc.

i'd be happy if usb audio works too, but it's not important.

> the last time i looked, i was left with a guess
> that the driver needed to support some unholy handshake with the
> built-in "Transaction Translator"; not sure if that's really the
> problem.  Geoff and Nemo worked on disabling various caches which
> fixed most earlier issues.

what the heck is a "transaction translator"? it sound evil. :D

>
> -Skip
>
>> On Mon Sep  6 13:03:54 EDT 2010, rminnich@gmail.com wrote:
>>> On Mon, Sep 6, 2010 at 9:52 AM, Nemo <nemo.mbox@gmail.com> wrote:
>>>> Iirc, there's still work to be done to get them working fully  
>>>> and  properly. But i may be mistaken.
>>>> I remember I had to add support for kbin and mousein, as Erik  
>>>> points out.
>>>
>>>
>>> Well, here is the kind of hackathon type of think it might be fun to
>>> do at IWP9. Get the right people in the room, work for 24 hours and
>>> get it right, either that or start hallucinating that we got it  
>>> right
>>
>> i like the idea.  unfortunately, iirc this problem hangs on  
>> specifications
>> which we don't have.  so perhaps it would be better to attack a  
>> problem
>> were we're not just guessing.

ron, you're making me wish i could go to iwp9, :) but erik's right.

>>
>> - erik
>
>




  reply	other threads:[~2010-09-06 21:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-06 14:43 Ethan Grammatikidis
2010-09-06 15:22 ` erik quanstrom
2010-09-06 16:52   ` Nemo
2010-09-06 17:02     ` ron minnich
2010-09-06 17:05       ` erik quanstrom
2010-09-06 17:26         ` ron minnich
2010-09-06 17:27           ` ron minnich
2010-09-06 21:15           ` erik quanstrom
2010-09-06 17:55         ` Skip Tavakkolian
2010-09-06 21:32           ` Ethan Grammatikidis [this message]
2010-09-06 19:51   ` geoff
2010-09-06 21:06     ` erik quanstrom
2010-09-06 22:29     ` Tristan Plumb

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=06D07BCD-9C82-4757-9C2C-25DC21256FD7@fastmail.fm \
    --to=eekee57@fastmail.fm \
    --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).