From mboxrd@z Thu Jan  1 00:00:00 1970
References: <AANLkTi=pq9ASxa5y53f2HUQ+6amvMmCCqAAwN-gzyns+@mail.gmail.com>
	<AANLkTimMN46BDskQRfLRNWVqnF1aTHgoUn3Ls+MKrBsH@mail.gmail.com>
	<AANLkTinqh7nEKRk-HFCO6130Z-KijNNLpCbvNzGEcf1+@mail.gmail.com>
From: Gorka Guardiola <paurea@gmail.com>
In-Reply-To: <AANLkTinqh7nEKRk-HFCO6130Z-KijNNLpCbvNzGEcf1+@mail.gmail.com>
Mime-Version: 1.0 (iPad Mail 8C148)
Date: Sun, 27 Feb 2011 09:51:20 +0100
Message-ID: <6436530622925022571@unknownmsgid>
To: Skip Tavakkolian <skip.tavakkolian@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] usb/disk nvram and pxeload
Topicbox-Message-UUID: b53862e4-ead6-11e9-9d60-3106f5b1d025

G.


On 27/02/2011, at 05:15, Skip Tavakkolian <skip.tavakkolian@gmail.com> wrote:

> That was the approach i was taking when ... ( i only need 512 bytes
> after MBR, what could possibly go wrong?!) I destroyed some
> memorabilia on that flash. Oh well; no big loss.
>
> for some reason setting nvram='#u/usb/ep6.0/data" nvroff=513 (is it 0
> or 1 origin?) nvrlen=512 didn't work. i guessed it might have been the
> fact that usbd started usb/disk; i was getting device busy.

No, that is wrong. I meant the data file of the disk  That data (of
the endpoint) is a communication
channel of the endpoint. The you need to speak the protocol... Which
is what usb/disk does.