On 2008-Aug-23 21:39:34 -0700, Kip Macy <[EMAIL PROTECTED]> wrote:
>There really isn't any magic to bringing up a port. You compile it,
>install it, and then run it until it breaks. Once it breaks you spend
>a lot of time instrumenting the code to track down what went wrong.
About what I expected.
Maxim Sobolev wrote:
Peter Jeremy wrote:
Is there a summary of the open issues somewhere? There are no sun4v
PRs open. http://wiki.freebsd.org/FreeBSD/sun4v effectively hasn't
been touched since November 2006 and suggests that the only critical
issue is lack of serial port support.
There is
> I can't find anything that suggests NetBSD runs on sun4v. Their sparc64
> port only covers the US-I/II families and there's no mention of sun4v.
OpenBSD/sparc64 runs UltraSPARC-T1 and UltraSPARC-T2 systems... and the
com port works too. ;)
In addition to UltraSPARC III, III+, IIIi, IV and Fuji
On Sat, Aug 23, 2008 at 9:34 PM, Sevan / Venture37
<[EMAIL PROTECTED]> wrote:
>
>
>> I can't find anything that suggests NetBSD runs on sun4v. Their sparc64
>> port only covers the US-I/II families and there's no mention of sun4v.
>
> OpenBSD/sparc64 supports the sun4v architecture & has done for
Hi Peter,
There really isn't any magic to bringing up a port. You compile it,
install it, and then run it until it breaks. Once it breaks you spend
a lot of time instrumenting the code to track down what went wrong.
Then, depending on the amount of technical insight you have in to the
issue, you g
On 2008-Aug-23 22:40:55 -0500, Mark Linimon <[EMAIL PROTECTED]> wrote:
>My understanding is the the port is in a pre-alpha state due to unfinished
>work in the kernel, so expecting there to be any userbase is premature.
Except that the wiki gives a far more optimistic picture.
>All of our 'new' a
On Sat, Aug 23, 2008 at 06:52:07PM -0700, Maxim Sobolev wrote:
> There is a better interpretation, which is that the only critical issue
> is lack of real users for this port, not lack of serial port support :).
My understanding is the the port is in a pre-alpha state due to unfinished
work in th
On Sat, Aug 23, 2008 at 6:52 PM, Maxim Sobolev <[EMAIL PROTECTED]> wrote:
> Peter Jeremy wrote:
>>
>> Is there a summary of the open issues somewhere? There are no sun4v
>> PRs open. http://wiki.freebsd.org/FreeBSD/sun4v effectively hasn't
>> been touched since November 2006 and suggests that the
Peter Jeremy wrote:
Is there a summary of the open issues somewhere? There are no sun4v
PRs open. http://wiki.freebsd.org/FreeBSD/sun4v effectively hasn't
been touched since November 2006 and suggests that the only critical
issue is lack of serial port support.
There is a better interpretatio
In message: <[EMAIL PROTECTED]>
Pietro Cerutti <[EMAIL PROTECTED]> writes:
: -BEGIN PGP SIGNED MESSAGE-
: Hash: SHA512
:
: Kris Kennaway wrote:
: | Just so everyone is on the same page, what is needed to keep sun4v
: | viable are people with experience with (or intention to lea
On 2008-Aug-22 17:04:00 +0200, Kris Kennaway <[EMAIL PROTECTED]> wrote:
>Just so everyone is on the same page, what is needed to keep sun4v
>viable are people with experience with (or intention to learn about) low
>level architectural and implementation details of the FreeBSD kernel
What documen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Kris Kennaway wrote:
| Just so everyone is on the same page, what is needed to keep sun4v
| viable are people with experience with (or intention to learn about) low
| level architectural and implementation details of the FreeBSD kernel and
| the sun
I would also like to help as well.
As KMacy knows before i asked a lot of questions for T2 types of
servers but unfortunately i have no more access to those kind of
hardware as well.
I;m willing to participate if a team will be formated.
___
freebsd-hacke
Nikolay Kalev wrote:
I would also like to help as well.
As KMacy knows before i asked a lot of questions for T2 types of
servers but unfortunately i have no more access to those kind of
hardware as well.
I;m willing to participate if a team will be formated.
Just so everyone is on the same page
14 matches
Mail list logo