[haiku-development] Re: R1a5 driver blocker issues (ATTN: Alexander)
- From: John Scipione <jscipione@xxxxxxxxx>
- To: "haiku-development@xxxxxxxxxxxxx" <haiku-development@xxxxxxxxxxxxx>
- Date: Thu, 29 May 2014 11:54:48 -0400
On Thu, May 29, 2014 at 11:17 AM, Jessica Hamilton
<jessica.l.hamilton@xxxxxxxxx> wrote:
> On 30 May 2014 01:55, John Scipione <jscipione@xxxxxxxxx> wrote:
>> On Thursday, May 29, 2014, Augustin Cavalier <waddlesplash@xxxxxxxxx> wrote:
>>>
>>> On Thu, May 29, 2014 at 5:21 AM, Julian Harnath
>>> <julian.harnath@xxxxxxxxxxxxxx> wrote:
>>>>
>>>> Instead of a fix for that, maybe it would be simpler if we could add
>>>> some kind of specific boot error message in this case? Is it possible
>>>> to catch this problem in the USB code and just panic with a specific
>>>> message? Most computers still have a few USB2-ports in addition to
>>>> USB3. If a non-haiku-savvy users sees "cannot find boot volume", they
>>>> will have no idea what's wrong. If the message in this case was "USB3
>>>> unsupported, please try booting with USB2 port" it would be clearer and
>>>> many could help themselves.
>>>
>>>
>>> How many? A lot of the newer machines I've seen (or used) are USB3 only by
>>> now. While that may be helpful, it would be a large hit to our hardware
>>> compatibility...
>>
>>
>> USB3 support is not a release blocker even for R1 IMHO. If we keep moving
>> the goal posts we'll never get to to goal. Yes, it would be nice to have and
>> we certainly won't reject well-formed patches to add the feature, but, its
>> absence shouldn't hold up the release.
>
> USB3 support, if only so far as to get mass storage and HID working,
> really is starting to become a critical issue. Things like graphics
> drivers can be disabled; no network makes things a little less fun,
> but you can still use it. I already have two separate machines which
> are USB3 only, and the list of new hardware that doesn't have USB2
> ports available continues to grow.
>
> And there were boot issues that were alpha blockers for R1A4; this
> issue needs to really be put high on the list for fixing before alpha5
> if at all possible.
>
> If someone could at least help with getting it building again, that
> alone would be a big step. I've tried myself already, but kept getting
> stumped with cryptic error messages I couldn't figure out.
I understand that USB3 support is sorely needed and is becoming more
relevant as time goes on, but, we're can't hold off the release of R1,
our first backwards compatible release, based on support for hardware
that didn't even exist when we started.
Let's get to R1 so we can then focus on the _really_ interesting stuff.
Other related posts:
