grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Important EHCI bugfix (Re: grub-2.02~beta1 happened)
Date: Fri, 20 Dec 2013 13:16:19 +0100	[thread overview]
Message-ID: <52B43513.9040206@gmail.com> (raw)
In-Reply-To: <52B35030.7060303@volny.cz>

[-- Attachment #1: Type: text/plain, Size: 1708 bytes --]

On 19.12.2013 20:59, Aleš Nesrsta wrote:
> Hi Vladimir,
> 
> it would be fine if the bugfix, posted by me in ML thread "EHCI/USBMS
> corrections" (12/16/2013), will be included in the final release. It
> solves serious bug.
> 
Check the git, it's already there, in cleaned up form.
> I tested it on four different PCs - it is working fine, I saw no
> negative results, and it helps on PCs where the problem, described in
> "flash drive timing out, can't boot vmlinuz/initrd (coreboot payload)",
> appeared.
> 
> Would be nice if the initial reporter "The Gluglug" will do test of this
> patch. Do you know him? Could you arrange such test with him? I don't
> see any further reaction from his side in ML thread "flash drive timing
> out, can't boot vmlinuz/initrd (coreboot payload)".
> 
> BR,
> Ales
> 
> Dne 19.12.2013 02:51, Vladimir 'φ-coder/phcoder' Serbinenko napsal(a):
>> Hello, all. I've just uploaded 2.02~beta1. This also means that we're
>> now in freeze. I'm willing to consider exceptions on case-by-case basis
>> but it would be exceptions. The major points to do before release:
>> - ARM64 loader.
>> - Yeeloong 3A support needs some love.
>> - XEN would probably need config adjustments.
>> - XNU loader needs fixes.
>> - NEWS needs contents.
>> - Documentation.
>> - Loads and loads of testing and some bugfixes.
>> ... 
>> _______________________________________________
>> Grub-devel mailing list
>> Grub-devel@gnu.org
>> https://lists.gnu.org/mailman/listinfo/grub-devel
>>
> 
> 
> 
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
> 



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 291 bytes --]

  reply	other threads:[~2013-12-20 12:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-19  1:51 grub-2.02~beta1 happened Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-19  5:43 ` Bruce Dubbs
2013-12-19 12:39   ` rijndael.c warning (was Re: grub-2.02~beta1 happened) Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-23 22:25     ` Mike Gilbert
2013-12-24 15:58       ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-19  6:38 ` grub-2.02~beta1 happened Andrey Borzenkov
2013-12-19  9:53   ` ext4 inline data (Re: grub-2.02~beta1 happened) Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-19 16:05     ` Andrey Borzenkov
2013-12-19 18:23       ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-19 19:59 ` Important EHCI bugfix " Aleš Nesrsta
2013-12-20 12:16   ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2013-12-20 17:57     ` Aleš Nesrsta

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52B43513.9040206@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).