Re: [9fans] printing from Plan 9

[Graham Gallagher]

>
>
> are there printers currently on the market which work well with Plan 9?
>
> A true Postscript printer (which will work) requires the OEM paying
royalties to Adobe so won't be the cheapest solution. You may be better off
sacrificing one of your old RPI boards to Linux and using that as your
common printer interface to the large set of supported printer devices.

Re: [9fans] Dvd-rw

[Graham Gallagher]

If 9660srv doesn't work then I'm no help.. If it's a UDF file system
(I think 9660 is ISO) the header should reveal the info and you'll
have to go to windows or Linux mount -t udf. The Linux driver is not
that big so I guess you could port it to P9.

Back in action? I saw some trouble maker called Tyger offering some
appropriate information a while back.


On 18 October 2016 at 14:41, Prof Brucee  wrote:
> Is there a secret incantation for reading a dvd-rw on plan9? Cdfs gives me a
> d000 file which I don't know what to with and 9660srv doesn't cope either.
>
> Brucee

Re: [9fans] Hosted Inferno on Raspberry Pi

[Graham Gallagher]

 To run inferno in fullscreen mode, would it be feasible to mmap the
 framebuffer address into the inferno address space and just write
 to it?

yep, the standard fb mmap code works but just needs a little tweaking
for the input event handling devices and removal of a few
unimplemented ioctls

[9fans] Hosted Inferno on Raspberry Pi

[Graham Gallagher]

The gcc flags: -march=armv6 -mfloat-abi=softfp -mfpu=vfp, will let you
compile the standard Inferno emu-g on the Raspberry Pi first go. Not
all the Linux VT interface ioctls are supported by the video driver so
a little work is needed to incorporate the framebuffer device.

Re: [9fans] mia

[Graham Gallagher]

 well not really we are going kashmir.

i thought kashmir was an alcohol free zone 'till i discovered led zeppelin

 i've fortified the CDM but what i need is a smallish rugged and bunny
 compliant box with a 250/320 disk in it, It\

 Toshiba 256GB solid state drive $500

Re: [9fans] sheevaplug port available

[Graham Gallagher]

 but i think inferno's logfs and ftl both assume 512 byte pages instead
 of 2048 byte pages that the sheevaplugs nand flash has (though it has
 writable subpages of 512 bytes), so i'm not sure how hard/easy an fs on
 it will be.

Some NAND flash definitions:
block = smallest erasable unit
page = smallest writable/readable unit.

Inferno's logfs limits the maximum number of pages per block to 32
because it uses a 32-bit integer bit mapping. The flash you're using,
has 64 pages per block.  You'll need to switch to vlong and change all
the associated bit bashing code.


 if anyone has tips  tricks for dealing with nand flashes, i'm interested
 in hearing them.  one question i have:  can you read the erase/program
 times from the chip? (hard-coding a table with properties based on data
 sheets isn't so great).  another: my new sheevaplug has samsung memory
 instead of hynix, so a different vendor id in the chip.  but the device
 id is the same (identifying chip properties (size, voltages, etc)).
 are those device id's standardized?  that would make a hard-coded table
 less annoying at least...

NAND flash technology is moving very quickly and new standards will
give you timing info. However, the hardware you mention will require
you to put the timing numbers in a table.

I don't know if device IDs are standardized, so I make no such assumption.

For Samsung chips, pure data retention is guaranteed for 10+ years.
Repetitive reading, without erasing the blocks is verified to 1E6
cycles. The number of program/erase operations is guaranteed up to 1E6
cycles if the system adopts ECC.

I've not seen much agreement with ECC and bad block mapping when it
comes to either linux or uboot. There are slabs of NAND specific code
in the linux tree that are never used. There are more slabs of code
that are used sometimes. You can do whatever you want.

I've only dealt with embedded systems and they're all different. Read
word size, write size,
it's all an experiment to what works. If you're lucky, you can put a
probe on a pin and look at a signal but normally it's just trial and
error.

Re: [9fans] sheevaplug port available

[Graham Gallagher]

 does plan 9 have a writable nand flash file system that does wear-leveling
 and such?

 could that be among the code for the bitsy?

The Bitsy does it all for NOR flash but sadly NAND flash is more
problematic. NAND flash is cheap and easy for the hardware guys (and
consumers) but it's a real hassle for programmers. If you're feeling
lucky, then its a simple extension from random access to page
read/write. If you care about reliability, then it's back to ECC
generation/checking and bad block mapping and wear leveling and
mirroring 

Re: [9fans] jjm

[Graham Gallagher]

do you reckon anyone will make dinner? 10am is an early start. perhaps
you need to track down TK

On 3/10/09, Bruce Ellis bruce.el...@gmail.com wrote:
 IWP92009-Bondi:

  http://www.chunder.com/stuff/IWP92009-Bondi/IWP92009-Bondi.pdf

  brucee