Haiku developer interviews in Deutschlandradio Kultur

Howdy,

For those who may have missed the recent announcement on the Haiku 
website, the culture-oriented radio station of the German national radio 
service, Deutschlandradio Kultur, will be airing an interview with Haiku 
developers Axel Dörfler, Ingo Weinhold, Michael Lotz and Stephan Aßmus 
that was recorded during the last BeGeistert 018 event.

* Date: February 2nd 2008
* Time: between 14:00 and 15:00 CET
* Live stream: http://www.dradio.de/dkultur/

A downloadable version will also be made available later. See the 
original announcement from Stephan Aßmus here:

http://www.haiku-os.org/news/2008-02-01/developer_interviews_in_deutschlandradio_kultur

Cheers,

Jorge Mare (a.k.a. Koki)

Haiku <at> SCaLE 6x conference reminder

Hello,

The SCaLE 6x Conference is around the corner, and Haiku will be there in 
full swing. This is the second year in a row that Haiku has a presence 
at SCaLE, and this time we are coming in through the big door. We will 
have a Haiku booth (#38) and one Birds of a  Feather (BoF) talk on 
Sunday, but the highlight of this event is that Haiku developer Bruno G. 
Albuquerque is a keynote speaker, and will be giving a Haiku talk on 
Saturday. This is something that you should not miss. :)

Our experience at SCaLE last year was great. Not only did we all have a 
great time showing off Haiku, but we loved the atmosphere as well as how 
well the ideas and concepts behind Haiku were received among the people 
that visited our booth and attended our two BoFs. We are looking forward 
to having a lot of fun this year too.

SCaLE is held at the Los Angeles Airport Westin Hotel on February 9 and 
10. All Haiku (or current/former BeOS) fans in the area or otherwise are 
welcome to join and hang out with us. If you have been lurking or 
watching the project from the sideline, this may be a good opportunity 
to finally meet some of the Haiku community members and learn more about 
our project.

We could also use a hand to man the Haiku booth. If you think you can 
help us, even if it is only for a few hours, please contact me using 
this contact form:

http://www.haiku-os.org/user/5/contact

Becoming booth staff will save you the admission fee to the expo (that's 

Haiku first impressions (last build)

Re: Haiku first impressions (last build)

is there any real version(hard drive installation) available with wifi  
support?????(ipw2100 or 2200))???? I don't really like to use vmware.

It would be great if there is beta version that can feature wifi support  
+ firefox/opera browser. That is all I need.

My first computer that I got was running BeOS but 3 months later they went  
out of business. I liked it a lot. Now I am running
linux but I wish that I could go back and run BeOS again.

-gs2501

On Fri, 01 Feb 2008 20:31:37 -0600, Michael Oliveira  
<michaelvoliveira@...> wrote:

> Hi folks,
>
> I've been playing with haiku in vmware today and I can say that are  
> solid and stable system!! it's amazing!!
>
> I like all!!
>
> Haiku behave like BeOS now, I'm not want use BeOS more!!
>
> I notice that Devices pref still not in development
>
> Why nightly builds remains only 20MB free space in the image?
>
> and that my realtek sound card don't play any sound, someone can say me  
> why? (HDA is coming?)
>
> and packge installer runs smoothly, but needs a better UI...
>
>
> Great job guys,,
> Haiku rocks!!
>
> Regards
> Michael Oliveira
>
>
>       Abra sua conta no Yahoo! Mail, o único sem limite de espaço para  
> armazenamento!
> http://br.mail.yahoo.com/

--

-- 
Ubuntu Linux + Opera Mail

Nasm

Hello,

Has anyone looked at porting a newer version of nasm than 0.98.35

I have some assembler sources that use SSE4 symbols and nasm won't
deal with them.

Anyone know of any gotchas in using a later nasm version?

--

-- 
Cheers
David

Re: Nasm

from http://nasm.sourceforge.net/
http://sourceforge.net/forum/message.php?msg_id=

But you should ask the nasm people about SSE4 and when it was first
introduced :)

I have looked at the code (0.98.35) but it looks like the beos specific
code are not in (if there are any) but configure don't work.. not in Zeta
1.21 anyway.

I have sent a mail to Realtech VR for help and perhaps the changes they did.

> Hello,
>
> Has anyone looked at porting a newer version of nasm than 0.98.35
>
> I have some assembler sources that use SSE4 symbols and nasm won't
> deal with them.
>
> Anyone know of any gotchas in using a later nasm version?
>
> --
> Cheers
> David
>
>

--

-- 
MVH
Fredrik Modéen

Re: Nasm

Yes I have grabbed the source from there and I am looking into getting
the current source working under BeOS but I was hoping someone else
might have done so already or have a better idea about what is needed.

Are Realtek VR still around, their website does not seem particularly
up to date.

On 02/02/2008, Fredrik Modéen <fredrik@...> wrote:
> from http://nasm.sourceforge.net/
> http://sourceforge.net/forum/message.php?msg_id=
>
> But you should ask the nasm people about SSE4 and when it was first
> introduced :)
>
> I have looked at the code (0.98.35) but it looks like the beos specific
> code are not in (if there are any) but configure don't work.. not in Zeta
> 1.21 anyway.
>
> I have sent a mail to Realtech VR for help and perhaps the changes they did.
>
> > Hello,
> >
> > Has anyone looked at porting a newer version of nasm than 0.98.35
> >
> > I have some assembler sources that use SSE4 symbols and nasm won't
> > deal with them.
> >
> > Anyone know of any gotchas in using a later nasm version?
> >
> > --
> > Cheers
> > David
> >
> >
>
>
> --
> MVH
> Fredrik Modéen
>
>
>

--

-- 
Cheers
David

Re: Nasm

> 
> Has anyone looked at porting a newer version of nasm than 0.98.35

I just played around with 2.01 last week a little bit.  I ran into problems
with it because of the use of newer posix definitions.  Since then I've
gotten sidetracked on writing some new posix headers (partly to learn posix
stuff).
Not being a gcc expert, I'm wondering how the implemented 64-bit code
affects the ability to compile it with gcc 2.95.  

> I have some assembler sources that use SSE4 symbols and nasm won't
> deal with them.
> 
> Anyone know of any gotchas in using a later nasm version?
> 

At this point, I only know of the need to define some of the newer posix
constants and macros.  I particularly ran into the need for the fprintf()
and fscanf() macros in inttypes.h.  Also UINT_64() in stdint.h.  I'm sure
there are plenty of other gotchas.

Curtis

Re: Nasm

Yep I am hitting the same problem.

I have just been adding the defines that are missing for the moment.

I am assuming that nasm will emit 64bit values when compiling asm
sources with 64bit code in them.  That shouldn't affect how gcc
compiles nasm.

Nasm is I believe written in standard c99 C code so gcc with a few
fixes for c99 compatability will be ok.

If not then I am going to have to look at alternatives.  (or most
likely just comment out the SSE4 stuff I am trying to get compiled
[probably a better idea anyway, who is running a BeOS machine on a
SSE4 capable CPU?])

On 04/02/2008, Curtis Wanner <katisu@...> wrote:
> >
> > Has anyone looked at porting a newer version of nasm than 0.98.35
>
> I just played around with 2.01 last week a little bit.  I ran into problems
> with it because of the use of newer posix definitions.  Since then I've
> gotten sidetracked on writing some new posix headers (partly to learn posix
> stuff).
> Not being a gcc expert, I'm wondering how the implemented 64-bit code
> affects the ability to compile it with gcc 2.95.
>
> > I have some assembler sources that use SSE4 symbols and nasm won't
> > deal with them.
> >
> > Anyone know of any gotchas in using a later nasm version?
> >
>
> At this point, I only know of the need to define some of the newer posix
> constants and macros.  I particularly ran into the need for the fprintf()
> and fscanf() macros in inttypes.h.  Also UINT_64() in stdint.h.  I'm sure
> there are plenty of other gotchas.

--

-- 
Cheers
David

Re: Nasm

Ok I have compiled a new version of nasm (2.01)

I did the following to compile it.

renamed their float.h float.c to nasmfloat.h nasmfloat.c and fix the
makefiles etc to cope.  This was done because their version of float.h
was being included instead of gcc's version.

Added the following defines to compiler.h  These are c99 constructs
that we don't have in our gcc headers.

#define	PRIu32			"u"
#define	PRIX32			"X"
#define	PRId32			"d"
#define	PRIX64			"X"
#define	PRId64			"d"
#define	PRIu64			"u"
#define	PRIx64			"x"
#define	PRIx32			"x"
#define	PRIx16			"x"
#define	PRIx8			"x"

#define INT32_MAX 2147483647
#define UINT64_C(val) val##ULL

Can anyone who knows more about what these values should be for BeOS
please verify my choices.

nasm 2.01 runs and compiles most of my asm files now.  It just seems
to be missing 2 commands.

If anyone wants a copy to try let me know.

--

-- 
Cheers
David