On 06/10/2012 12:01 PM, andrey mirtchovski wrote:
I like the "or MIME" part. ;)
i forgot to include a reference: http://mail.9fans.net/listinfo/9fans
On above said page, it would be nice to have the following as
active/click-able links:
http://plan9.bell-labs.com/plan9/
http://plan9.bell-l
OK, solved. This motherboard (or bios) gives the io apic an id of 0,
same as the boot processor's local apic. The unexpected aliasing
causes the lapic (virtual) address to be overwritten by the ioapic
address, so the lapic timer code is looking in the wrong place for its
registers.
This was actu
On Mon Jun 11 07:02:26 EDT 2012, 9f...@hamnavoe.com wrote:
> OK, solved. This motherboard (or bios) gives the io apic an id of 0,
> same as the boot processor's local apic. The unexpected aliasing
> causes the lapic (virtual) address to be overwritten by the ioapic
> address, so the lapic timer c
> * Raspberry Pi
At least two 9fans are in the order queue for one of these.
On Jun 11, 2012 10:03 AM, "Richard Miller" <9f...@hamnavoe.com> wrote:
>
> > * Raspberry Pi
>
> At least two 9fans are in the order queue for one of these.
>
>
I think three including me actually. The drivers factor might only make it
a good cpu server methinks. I would totally love one as a termin
> I think three including me actually. The drivers factor might only make it
> a good cpu server methinks. I would totally love one as a terminal though.
sadly, the 10/100 ethernet is provided through a flakey usb hub
(http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7380)
for me, that's th
On Sun, 10 Jun 2012 18:19:20 -0400
Comeau At9Fans wrote:
> Ok, so, unless I was asleep at the wheel following these
> discussions, there's been a few "mini PCs" to come about lately:
>
> * Raspberry Pi
> * Cotton Candy
> * Mele A1000
> * MK802
>
> We have a small number of the latter (MK802 run
On Sun, 2012-06-10 at 18:19 -0400, Comeau At9Fans wrote:
> * Raspberry Pi
> * Cotton Candy
> * Mele A1000
> * MK802
Some other _pricier_ products to consider (and a larger variety of
integrated components):
* Beagleboard
* Beaglebone
* Pandaboard
* Pico-ITX formfactor x86 motherboard
looking for more pleasing fonts I came across dejavu which are
downloadable from http://dejavu-fonts.org/wiki/Download
ttf2subf deals with them relatively well in antialiased mode and
relatively badly in mono mode, but the results for antialiased are
good enough to share, i think:
dejavusans, siz
On Mon, Jun 11, 2012 at 1:14 PM, Winston Weinert wrote:
> On Sun, 2012-06-10 at 18:19 -0400, Comeau At9Fans wrote:
>> * Raspberry Pi
>> * Cotton Candy
>> * Mele A1000
>> * MK802
>
> Some other _pricier_ products to consider (and a larger variety of
> integrated components):
> * Beagleboard
> * Bea
what about teg2 for which geoff announced support recently?
btw, i have two raspberry pi at home now. i would like to run plan9
and inferno (at least emu) on it as soon as possible.
dharani
On Mon, Jun 11, 2012 at 2:07 PM, John Floren wrote:
> On Mon, Jun 11, 2012 at 1:14 PM, Winston Weinert w
On Mon Jun 11 17:07:15 EDT 2012, mirtchov...@gmail.com wrote:
> looking for more pleasing fonts I came across dejavu which are
> downloadable from http://dejavu-fonts.org/wiki/Download
>
[...]
>
> coverage is so-so, but there are latin/greek/cyrillic ttfs available
> too. i didn't try them out.
On Mon, Jun 11, 2012 at 2:16 PM, erik quanstrom wrote:
> On Mon Jun 11 17:07:15 EDT 2012, mirtchov...@gmail.com wrote:
>> looking for more pleasing fonts I came across dejavu which are
>> downloadable from http://dejavu-fonts.org/wiki/Download
>>
> [...]
>>
>> coverage is so-so, but there are lati
> it really is a trick finding decent coverage and a good looking font.
> good coverage seems to be more important as folks assume unicode.
unicover.txt has a detailed description of the coverage. langcover.txt
notes the languages covered. it seems to be better than what I
expected.
is libdraw ab
On Mon Jun 11 17:37:43 EDT 2012, mirtchov...@gmail.com wrote:
> > it really is a trick finding decent coverage and a good looking font.
> > good coverage seems to be more important as folks assume unicode.
>
> unicover.txt has a detailed description of the coverage. langcover.txt
> notes the langu
> Vera (I think from your contrib) works very well for me, I find that
> it looks good and has good enough coverage for all my uses.
ah, great.
> The biggest challenge with Plan 9 fonts is getting the heights right;
> often converted ttfs will have the bottom of "g" and a lot of the
> non-ASCII c
> Vera (I think from your contrib) works very well for me, I find that
> it looks good and has good enough coverage for all my uses.
I loved vera until I switched from drawterm to native. Lately,
lucidasans is very comfortable.
-sl
> The biggest challenge with Plan 9 fonts is getting the heights right;
> often converted ttfs will have the bottom of "g" and a lot of the
> non-ASCII characters cut off at either top or bottom.
that's why I try to stay in the very narrow band of sizes 13 and 14 :)
bdf2subf did a much better job
On Mon Jun 11 17:58:28 EDT 2012, s...@9front.org wrote:
> > Vera (I think from your contrib) works very well for me, I find that
> > it looks good and has good enough coverage for all my uses.
>
> I loved vera until I switched from drawterm to native. Lately,
> lucidasans is very comfortable.
why
> that's why I try to stay in the very narrow band of sizes 13 and 14 :)
> bdf2subf did a much better job at properly sizing fonts.
>
> now that you've made me look, there's a magic constant used for sizing
> in main.c:611 of freetype-plan9 (ttf2subf). the constant 64 works well
> for sizes 13-14
On Mon, 11 Jun 2012 17:58:39 -0400
erik quanstrom wrote:
> On Mon Jun 11 17:58:28 EDT 2012, s...@9front.org wrote:
> > > Vera (I think from your contrib) works very well for me, I find that
> > > it looks good and has good enough coverage for all my uses.
> >
> > I loved vera until I switched fr
> i don't think it's a sizing thing. i think ttf2subf is somehow getting
> the baseline wrong for letters like Â. (try cyberbit even at 14.)
I don't see height issues with cyberbit (at "magic" constant of 64
even) but I am seeing width issues, especially the '0', which seems to
always be chopped
> http://mirtchovski.com/screenshots/cyberbit-erik2.png
this was generated with
FT_Set_Char_Size(font.face, font.size*72, font.size * 64, 72, 72);
according to the documentation, the previous value of 0 defaults to
the height, which is font.size*64...
>> I loved vera until I switched from drawterm to native. Lately,
>> lucidasans is very comfortable.
>
> why would native make a difference?
In native, I no longer benefit from X11's rendering. Here, blurry
fonts look blurry.
-sl
On Mon Jun 11 18:36:04 EDT 2012, mirtchov...@gmail.com wrote:
> > i don't think it's a sizing thing. i think ttf2subf is somehow getting
> > the baseline wrong for letters like Â. (try cyberbit even at 14.)
>
> I don't see height issues with cyberbit (at "magic" constant of 64
> even) but I am s
On Mon Jun 11 19:32:19 EDT 2012, s...@9front.org wrote:
> >> I loved vera until I switched from drawterm to native. Lately,
> >> lucidasans is very comfortable.
> >
> > why would native make a difference?
>
> In native, I no longer benefit from X11's rendering. Here, blurry
> fonts look blurry.
i
this is the incantation i'm using. the second argument is zero, not
font.size*72
as in your example
if(FT_Set_Char_Size(font.face, 0, font.size * 64, 72, 72) != 0)
sysfatal("FT_Set_Char_Size: status=%d\n", status);
- erik
>> In native, I no longer benefit from X11's rendering. Here, blurry
>> fonts look blurry.
>
> i'm not having that problem. but that might be because of the details of
> the conversion to font, or due to personal sensitivity to subpixeling.
In my case it's the same several machines used with the
my source is here:
http://ftp.quanstro.net/other/ttf2subf.tbz
i included the executable i last used as its origin is somewhat in doubt.
i never use the good cycles for fiddle around with fonts. ☺
- erik
> In my case it's the same several machines used with the same screens. The
> only change was the local operating system. From drawterm on OpenBSD
> I thought vera was very nice (and used it for around a year); in Plan 9 native
> on the same machine vera looks blurry. I realize this is subjective t
i added a little toy program to radar(1) (contrib quanstro/radar)
to continuously display the current radar image called radarloop.
if you're feeling like you've got time on your hands, try
overlaying overlapping radars (by taking the data from the nearest
radar) so one can pan about.
- erik
> sadly, the 10/100 ethernet is provided through a flakey usb hub
I think the 'cheap arm dev board' bandwagon will always suffer in this
regard, since the phones these SoCs were designed for don't even come
close to needing gbe
On 6/11/12, Tharaneedharan Vilwanathan wrote:
> what about teg2 for
On Mon, Jun 11, 2012 at 9:38 PM, Nick LaForge wrote:
>> sadly, the 10/100 ethernet is provided through a flakey usb hub
>
> I think the 'cheap arm dev board' bandwagon will always suffer in this
> regard, since the phones these SoCs were designed for don't even come
> close to needing gbe
>
Gurup
On Tue Jun 12 00:39:16 EDT 2012, nicklafo...@gmail.com wrote:
> > sadly, the 10/100 ethernet is provided through a flakey usb hub
>
> I think the 'cheap arm dev board' bandwagon will always suffer in this
> regard, since the phones these SoCs were designed for don't even come
> close to needing gb
On Tue, Jun 12, 2012 at 12:51:28AM -0400, erik quanstrom wrote:
> On Tue Jun 12 00:39:16 EDT 2012, nicklafo...@gmail.com wrote:
> > > sadly, the 10/100 ethernet is provided through a flakey usb hub
> >
> > I think the 'cheap arm dev board' bandwagon will always suffer in this
> > regard, since the
Sure. But the Sheevaplug (same SoC) is now 3 years old, and it looks
like the whole 'plug-computer' thing never took off. Since phones
seem to be the only consistent market for fast Arm SoCs, we're likely
to see one with usb3 before gbe. But I'll shut up now in deference to
somebody with actual
"failure of vision"
On 12 June 2012 00:56, Kurt H Maier wrote:
> Why do I have to invent a point to your message?
Evaluations of the Sheevaplug in particular revealed it tended to
overheat badly if you put any significant load on the networking
components. Heating problems combined with poor quality control would
be my guess as to why that whole thing never flew.
On Tue, Jun 12, 2012 at 01:08:38AM -0400, Charles Forsyth wrote:
> "failure of vision"
>
I think a sunken ship and an unidentified attack vessel are about as
much use to a man stranded on a tiny island as high-throughput wired
networking is to low-power compute devices.
On Tue Jun 12 01:14:34 EDT 2012, kh...@intma.in wrote:
> On Tue, Jun 12, 2012 at 01:08:38AM -0400, Charles Forsyth wrote:
> > "failure of vision"
> >
>
> I think a sunken ship and an unidentified attack vessel are about as
> much use to a man stranded on a tiny island as high-throughput wired
> n
Well, I'm the zaurus 'somebody'. You're welcome to the kernel source,
and I can provide some help with getting it going. For my purposes,
performance is pretty sprightly. I still use it for writing or reviewing
the odd bit of code or text editing. Yes, viewing pdf's is slow
but I assume that is bec
41 matches
Mail list logo
