Date: Sun, 13 Mar 2005 22:05:09 -0700 From: Scott Long <scottl@samsco.org> To: obrien@freebsd.org Cc: re@freebsd.org Subject: Re: Blade 100 w/ 5.4-PRERELEASE console Message-ID: <42351B85.20901@samsco.org> In-Reply-To: <20050314030514.GB18526@dragon.NUXI.org> References: <20050312062214.GH10159@hex.databits.net> <20050312181935.A90975@newtrinity.zeist.de> <20050313211440.GB1470@dragon.NUXI.org> <20050313223350.J55534@newtrinity.zeist.de> <20050314030514.GB18526@dragon.NUXI.org>
next in thread | previous in thread | raw e-mail | index | archive | help
David O'Brien wrote: > On Sun, Mar 13, 2005 at 10:33:50PM +0100, Marius Strobl wrote: > >>On Sun, Mar 13, 2005 at 01:14:40PM -0800, David O'Brien wrote: >> >>>On Sat, Mar 12, 2005 at 06:19:35PM +0100, Marius Strobl wrote: >>> >>>>On Sat, Mar 12, 2005 at 12:22:14AM -0600, Will Andrews wrote: >>>> >>>>>mess with the OBP variables. I believe this is needless pain for >>>>>users trying to install FreeBSD on their Blade 100s (and possibly >>>>>other models). >>>> >>>>No, this is a nit which easily can be worked around. A real pain is >>>>that binutils are broken on sparc64 and users have to manually apply >>>>a patch to the base src and recompile binutils in order to be able >>>>to build a number of ports. >>> >>>Applying a patch that is running work around is a nit which can be easily >>>worked around. NOT being able to boot to apply a patch isn't. >>> >> >>I don't get what you try to say with the first sentence but the >>work-around to be able to boot was to set both input-device and >>output-device to ttya. I suggested you to do just this three >>times. > > > You suggested it on Friday. Why do you think I just stumbled upon it on > Friday? It took up considerable amount of my FreeBSD before I figured > out the bad commit. Its lovely that a commit that breaks things is so > fought for to remain in the tree. > > AND if you've been using sparc hardware for the past 15 years, this is > totally non-intuiative. > > So now I'm taking your position -- I'm telling you a work around for what > you feel is a big problem -- apply Kris' patch. > David 1) The work that is ongoing is with the console drivers will eventually allow more comprehensive console support, something that sparc64 is lacking. I'm personally quite happy that several people are stepping forward and giving sparc64 the care and feeding that it has lacked almost since its inception. 2) The breakage to Blade1x0 is quite unfortunate, but an actual fix was provided in a very reasonable amount of time. While it was definitely frustrating for you since you bore the brunt of isolating the problem, your effort and troubleshooting helped idenitfy the problem so that everyone else could benefit from the fix. At the macro scale, your time was not wasted, though I'm sure that at the micro scale it was quite painful to not be able to do the work that you actually wanted to do. Your teamwork here is noted and definitely appreciated. We've all suffered from breakage at the hands of others due to oversight or poor design, but working through it is what makes FreeBSD better. Thank you for your perserverance with the ATA and console problems. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42351B85.20901>