On Tue, Jan 26, 2016 at 03:19:45PM +0100, Laszlo Ersek wrote:
> >> Is this wise? It looks like BDS history repeating itself :-/
> >
> > Well, medium-term, I'd (optimally) like to see ArmVirtPkg split and go
> > into OvmfPkg one end and ArmPkg the other.
> >
> > But when Laszlo started out with A
On 01/26/16 15:48, Ryan Harkin wrote:
> On 26 January 2016 at 14:19, Laszlo Ersek wrote:
>> On 01/26/16 10:40, Leif Lindholm wrote:
>>> On Tue, Jan 26, 2016 at 09:12:39AM +, Ryan Harkin wrote:
> However there seems to be
> some interference from "ArmPlatformPkg/Library/PlatformIntelBds
On 26 January 2016 at 14:19, Laszlo Ersek wrote:
> On 01/26/16 10:40, Leif Lindholm wrote:
>> On Tue, Jan 26, 2016 at 09:12:39AM +, Ryan Harkin wrote:
However there seems to be
some interference from "ArmPlatformPkg/Library/PlatformIntelBdsLib" that
is supposed to connect PcdDef
On 01/26/16 10:40, Leif Lindholm wrote:
> On Tue, Jan 26, 2016 at 09:12:39AM +, Ryan Harkin wrote:
>>> However there seems to be
>>> some interference from "ArmPlatformPkg/Library/PlatformIntelBdsLib" that
>>> is supposed to connect PcdDefaultConInPaths and PcdDefaultConOutPaths.
>>> In order t
On Tue, Jan 26, 2016 at 09:12:39AM +, Ryan Harkin wrote:
> > However there seems to be
> > some interference from "ArmPlatformPkg/Library/PlatformIntelBdsLib" that
> > is supposed to connect PcdDefaultConInPaths and PcdDefaultConOutPaths.
> > In order to experiment with F9, Roy massaged the las
aszlo Ersek [mailto:ler...@redhat.com]
>> Sent: Friday, January 22, 2016 3:56 AM
>> To: Ryan Harkin
>> Cc: Ni, Ruiyu ; Leif Lindholm
>> ; edk2-de...@ml01.01.org; Zeng, Star
>> ; Ard Biesheuvel ; Roy Franz
>>
>> Subject: Re: [edk2] [PATCH 3/3] MdeModulePkg: T
tar ; Ard Biesheuvel
> ; Roy Franz
> Subject: Re: [edk2] [PATCH 3/3] MdeModulePkg: TerminalDxe: select the UART's
> default receive FIFO depth
>
> On 01/21/16 20:47, Ryan Harkin wrote:
>> On 21 January 2016 at 18:14, Laszlo Ersek wrote:
>>> On 01/21/16 18:57, Ryan
...@ml01.01.org; Zeng, Star ; Ard Biesheuvel
; Roy Franz
Subject: Re: [edk2] [PATCH 3/3] MdeModulePkg: TerminalDxe: select the UART's
default receive FIFO depth
On 01/21/16 20:47, Ryan Harkin wrote:
> On 21 January 2016 at 18:14, Laszlo Ersek wrote:
>> On 01/21/16 18:57, Ryan Harkin wr
On 01/21/16 20:47, Ryan Harkin wrote:
> On 21 January 2016 at 18:14, Laszlo Ersek wrote:
>> On 01/21/16 18:57, Ryan Harkin wrote:
>>> On 21 January 2016 at 17:19, Laszlo Ersek wrote:
>>
Ryan, can you please test the following configuration:
- your PCD update in place, but this three-par
On 21 January 2016 at 18:14, Laszlo Ersek wrote:
> On 01/21/16 18:57, Ryan Harkin wrote:
>> On 21 January 2016 at 17:19, Laszlo Ersek wrote:
>
>>> Ryan, can you please test the following configuration:
>>> - your PCD update in place, but this three-part series of mine
>>> *reverted*
>>>
>>> Thi
On 01/21/16 18:57, Ryan Harkin wrote:
> On 21 January 2016 at 17:19, Laszlo Ersek wrote:
>> Ryan, can you please test the following configuration:
>> - your PCD update in place, but this three-part series of mine
>> *reverted*
>>
>> This should break the cursor movement keys again, and also bre
dePkg follow
>>> standards strictly.
>>>
>>> (3) We more or less patched the same for ArmVirtQemu (please refer to
>>> git commit a51c1699), but differently. That difference is due to the
>>> fact that ArmVirtQemu uses its own, independent PlatformBdsLib
On 21 January 2016 at 17:44, Leif Lindholm wrote:
> On Thu, Jan 21, 2016 at 05:36:41PM +, Ryan Harkin wrote:
>> On 21 January 2016 at 17:32, Leif Lindholm wrote:
>> > On Thu, Jan 21, 2016 at 06:19:22PM +0100, Laszlo Ersek wrote:
>> >> Anyway, another question (for the ArmPlatformPkg maintaine
On Thu, Jan 21, 2016 at 05:36:41PM +, Ryan Harkin wrote:
> On 21 January 2016 at 17:32, Leif Lindholm wrote:
> > On Thu, Jan 21, 2016 at 06:19:22PM +0100, Laszlo Ersek wrote:
> >> Anyway, another question (for the ArmPlatformPkg maintainers as well):
> >> do you guys think that the PCD update
On 21 January 2016 at 17:32, Leif Lindholm wrote:
> On Thu, Jan 21, 2016 at 06:19:22PM +0100, Laszlo Ersek wrote:
>> Anyway, another question (for the ArmPlatformPkg maintainers as well):
>> do you guys think that the PCD update in question should be commited to
>> the repo, for the FVP (and maybe
On Thu, Jan 21, 2016 at 06:19:22PM +0100, Laszlo Ersek wrote:
> Anyway, another question (for the ArmPlatformPkg maintainers as well):
> do you guys think that the PCD update in question should be commited to
> the repo, for the FVP (and maybe Foundation) DSC files? After all those
> are mostly use
t;> ("ArmVirtPkg/Library/PlatformIntelBdsLib"). Hence a51c1699 isn't
>> portable to "ArmPlatformPkg/Library/PlatformIntelBdsLib", which is used
>> by FVP. But the method described in (1) should work for you.
>>
>> Thanks
>> Laszlo
>>
>
;t seem to know about TTYTERMTYPE
>>> - if you change the setting, you can only commit it with F10,
>>> apparently, which doesn't work to begin with.
>>> ... Wait, if you keep exiting the dialogs (not discarding the
>>> changes!), ultimately it will as
gt;> changes!), ultimately it will ask you about saving changes.
>>
>> If you apply the attached patch, you should be able to select VT_TTY in
>> the above menu option, in the Intel BDS. After that (possibly after a
>> reboot), F9 should also start to work. Can you test thi
he data. I remember discussing
this with Roy when he was making his TTY changes elsewhere too. I
makes me weak...
> Thanks
> Laszlo
>
>>
>>
>>> Regards,
>>> Ray
>>>
>>>
>>> -Original Message-
>>> From: Ryan Harkin [
;>>>>
>>>>> No clue, sorry. All we determined was that the FIFO depth of 1 caused
>>>>> the PL011Uart library to disable queueing on the device completely.
>>>>> Apparently, for handling isolated scan codes, no FIFO logic is necessary
>
gt;>>> scan codes didn't.)
>>>>
>>>
>>> I don't know if it's related, but when looking into why copy/paste
>>> doesn't work past one FIFO length, another Linaro team proposed that
>>> the timeout was too short for our baud rate.
, I fully agree that TerminalDxe should be able to work with any
>>>> SerialIO protocol instance, regardless of what UART driver produced it.
>>>>
>>>> However, the consequence that I draw from this requirement is different
>>>> from yours. My argum
t; SerialIO protocol instance, regardless of what UART driver produced it.
>>>>
>>>> However, the consequence that I draw from this requirement is different
>>>> from yours. My argument goes, if TerminalDxe cannot (and it should not)
>>>> as
>> Ray
>>>
>>> -Original Message-
>>> From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of
>>> Laszlo Ersek
>>> Sent: Thursday, January 21, 2016 11:23 AM
>>> To: Ni, Ruiyu
>>> Cc: Leif Lindholm ;
anks
> Laszlo
>
>>
>> Regards,
>> Ray
>>
>> -Original Message-
>> From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of
>> Laszlo Ersek
>> Sent: Thursday, January 21, 2016 11:23 AM
>> To: Ni, Ruiyu
>> Cc: Le
ould see, so we
> should try to conform in the reference implementation.
>
> But, whatever works. Feel free to revert my patches, or restore those
> bits as part of another solution.
>
> Thanks
> Laszlo
>
>>
>> Regards,
>> Ray
>>
>> -Original
.@lists.01.org] On Behalf Of Laszlo
Ersek
Sent: Thursday, January 21, 2016 11:23 AM
To: Ni, Ruiyu
Cc: Leif Lindholm ; edk2-de...@ml01.01.org; Ryan
Harkin ; Zeng, Star ; Ard
Biesheuvel
Subject: Re: [edk2] [PATCH 3/3] MdeModulePkg: TerminalDxe: select the UART's
default receive FIFO depth
On
hanks
Laszlo
>
> Regards,
> Ray
>
> -Original Message-
> From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Laszlo
> Ersek
> Sent: Tuesday, January 19, 2016 9:54 PM
> To: edk2-de...@ml01.01.org
> Cc: Ryan Harkin ; Zeng, Star ;
> L
k2] [PATCH 3/3] MdeModulePkg: TerminalDxe: select the UART's
default receive FIFO depth
The Serial IO protocol instances provided by SerialDxe and consumed by
TerminalDxe come with a Mode.ReceiveFifoDepth=1 default setting, as
required by UEFI 2.5.
Although Te
The Serial IO protocol instances provided by SerialDxe and consumed by
TerminalDxe come with a Mode.ReceiveFifoDepth=1 default setting, as
required by UEFI 2.5.
Although TerminalDxe calls EFI_SERIAL_IO_PROTOCOL.SetAttributes() in the
TerminalDriverBindingStart() and TerminalConInTimerHandler() fun
31 matches
Mail list logo
