News catchup - May 28th, 2008
  • Haiku Code Drive 2008: $7070.54 has been raised to date ! This is truly great support from our community.  There still is a need for $500 in order to reach the “3 students” mark. Those would could afford a donation and who didn’t make it yet please, this is the moment: donate now !    Also the poll is running to choose between students projects. To vote you need to create an acccount on the Haiku-os website.

  • François Revol Laurent “LoLL” JEAN-RIGAUD, is the proud father of a new little son: Mathias. Compliments (and sorry for my big inexcusable confusion :-) !

  • Rudolf Cornelissen posted a kind of “keepalive” message on his blog telling us what he is / he will work on. The BeOS/Haiku developer Matt Madia decided to thank Rudolf for his contribution by sending him two PCI-E display adapters: a Geforce 7300LE (G72) and a Geforce 8500GS (G86).

  • Haikuware’s June 1st Thank You Awards: Nominees are Michael “mmlr” Lotz – for having developped USB OHCI support and the mixed GCC2/4 environment, Gerald Zajac – for the S3 Trio, Virge and Savage graphic driver, François “mmu_man” Revol – for the USB Webcam Add-On and the PPC Port, Stefano “Jack Burton” Ceccherini – for his work on the Interface Kit and Terminal, and, last but not least :-), Tako “0033” Lansbergen – for the Haiku native IDE Niue. Please go cast your vote here.

  • Haikuware discusses also new ideas for future bounties here. A documentation as well as  hardware 3d acceleration bounties are considered;

  • Haiku-os developer Stephan Aßmus posted an article entitled “Steady Progress towards Alpha 1“. A very interresting read.

  • Sikosis et Dennis d’Entremont finished the mixing of the 14th edition of the popular Haiku Podcast.

  • Remeber my post “Bifuzz and 4 GB memory barrier” ? Blibbering Humdinger posted his point of view on the subject in an article to be found here telling us that if using 64 bits there would be no such barrier.  He is advocating the idea of Haiku going 64 bits ASAP. Ingo Weinhold’s advice is going in the opposite direction as you can read in the Haiku Gazette (in german, goolge traslation here).

A nice day to you all, take care !

Category: News   -   Comments RSS   -   Post a Comment   -   Trackback  

« »


9 Comments on 2008-05-28 at 06:26 (Reply)
It seems Humdinger's has problem to serve http at the moment...
Stephen B. on 2008-05-28 at 15:09 (Reply)
The BeOS/Haiku developer Matt Madia decided to thank Rudolf for his contribution by sending him two PCI-E display adapters: a Geforce 7300LE (G72) and a Geforce 8500GS (G86).

Hmmm... two video cards from Matt Madia, would that qualify as a "Madia Kit"? :)
LoLL ! on 2008-05-29 at 13:35 (Reply)

Hum... i will be very angry if Francois is the father of my son....

Webmaster of
Stephen B. on 2008-06-01 at 00:15 (Reply)
Don't worry, Manette - in the first month BeOSNews was live, I managed to mix up looncraz and Bryan Varner :)
Blibbering Humdinger on 2008-06-12 at 00:00 (Reply)
Good to see I'm "Blibbering Humdinger" but my point seems to be getting lost the more I see comments made about my article. I this might be due to actual language translation but I digress.

I'm not sure what you mean about the "if using 64 bits there would be no such barrier" since that's a broken sentence but the point is while the kernel could be limited like the BeOS kernel hack they came up with tie limit RAM to say 512mb to keep it from KDL'ing? Why would you want to limit or break things right off the bat. Haiku is not even at Alpha 1 yet but risks being left behind without crippling itself to function on stuff that being sold all over the place. You can buy cheesy stock OEM machines at Best Buy now with 6 gigs of RAM, but a 32bit OS won't handle that.

The Haiku Gazette article also doesn't make sense as the translation leaves a few things too broken for me to get the gist of. It almost reads like I failed to mention todays 64bit CPU's won't run 32bit code but I did say that. My point was by the time R1 comes around, will it even work on common hardware? Or will it require extra code to break and limit things?

I'm well aware of the fact the majority of the 64bit CPU in the wild are running Windows XP 32bit and even Vista 32bit, but that's right now. I'm seeing more and more media center machines and gaming machines hitting the common shelves and they are leaving the 32bit Vista behind for the 64bit as the machines are shipping with 4+ gigs of RAM.

The Haiku Gazette article in #4 (again the translation is rough) makes it sound as if these are reasons to stay 32bit, but why? Do they plan on staying 32bit forever? I don't see the purpose of hanging on to this, get over the hump move to a 64bit addressing space, and focus on what Be was about, forward looking. on 2008-06-12 at 08:39 (Reply)
SHED said "I’m not sure what you mean about the “if using 64 bits there would be no such barrier”

I was trying to say that if Haiku (or any other OS/Kernel) is 64 bits it (application or OS/Kernel) wouldn't be limited to the 4 Gbyte memory limit (whether per application or as seen by the OS/Kernel).

Am I wrong ?

About your point on the 64 bits topic: I think you tell us that at the time R1 will be released 4Gbyte+ configurations will be commonly found (as they already are affordable today). So you think we should not make Haiku (seen as) "limited" (if it still is 32 bit at that time there will be a need for a "hack" hiding the unusable memory to the OS/kernel and applications). You think Haiku should be focused on the future.

Again, am I right ?

I was just trying to summarize the information without taking a position about the "strategical" question: should Haiku go 64 bits (ASAP)...
[...] topic of my previous “news catchup” item was about the 64 bit question and the relation to the 4 Gbyte memory barrier Biffuz [...]
Blibbering Humdinger on 2008-06-12 at 17:24 (Reply)
I think you have the idea ya, basically you can't address that much the over 4gig mark in 32bit mode, I think you however point out a distinction I wasn't even thinking about, a 32bit app run on the 64bit OS. Basically what I'd like to see happen is Haiku move to the 64bit code base so there is no stupid road blocks after the fact. If they move to a 64bit code base and then either make a layer to run the 32bit apps much like Win XP does for 16bit apps or Win XP 64 does for 32bit apps. OR they create a system to easily bring the 32bit apps to the 64bit base.

Again I know this is a lot of work but it's going to need to be done someday, unless they really do think they will stay 32bit forever, so they might as well build on the 64bit base rather then slip it in as an afterthought. 64bit is the norm and I soo dearly want to see BeOS alive and well no matter what it's name might be, but I also don't want to have to keep old crappy machines kicking around to use it, nor do I want to have it omit half my machines spec to function.

I think we all want BeOS to rise and kick serious ass, and I just don't think a 32bit code base can pull it off as everything is 64bit and things are pushing the need to address more and more memory space. This doesn't mean Haiku will be a pig on system resources to need to utilize 16gigs of RAM, it just means if I have 16gigs of RAM in my machine I want to use it. I didn't buy 16gigs of RAM to use 4gigs.

I'm sure we can expect issue with obscure or bleeding edge hardware but utilizing RAM or or full CPU potential is so base I don't see how this can be an omitted focus. We're on 64bit chips, so let's use 64bits, not 32!
Roadrunner on 2008-06-22 at 14:40 (Reply)
I fully agree with you.

Leave a Reply

Design Copyright © Meghan Davison 2008, Content Copyright © . All rights reserved.