Am 14.01.2019 um 19:26 schrieb Marek Vasut:
On 1/14/19 4:21 PM, Simon Goldschmidt wrote:
Am 08.01.2019 um 13:56 schrieb Marek Vasut:
On 1/8/19 1:42 PM, Simon Goldschmidt wrote:
On Tue, Jan 8, 2019 at 1:08 PM Marek Vasut wrote:
On 1/8/19 1:06 PM, Simon Goldschmidt wrote:
On Tue, Jan 8,
On 1/14/19 4:21 PM, Simon Goldschmidt wrote:
> Am 08.01.2019 um 13:56 schrieb Marek Vasut:
>> On 1/8/19 1:42 PM, Simon Goldschmidt wrote:
>>> On Tue, Jan 8, 2019 at 1:08 PM Marek Vasut wrote:
On 1/8/19 1:06 PM, Simon Goldschmidt wrote:
> On Tue, Jan 8, 2019 at 12:20 PM Marek Vasut
Am 08.01.2019 um 13:56 schrieb Marek Vasut:
On 1/8/19 1:42 PM, Simon Goldschmidt wrote:
On Tue, Jan 8, 2019 at 1:08 PM Marek Vasut wrote:
On 1/8/19 1:06 PM, Simon Goldschmidt wrote:
On Tue, Jan 8, 2019 at 12:20 PM Marek Vasut wrote:
On 1/8/19 7:41 AM, Simon Goldschmidt wrote:
On Mon,
On 1/8/19 1:42 PM, Simon Goldschmidt wrote:
> On Tue, Jan 8, 2019 at 1:08 PM Marek Vasut wrote:
>>
>> On 1/8/19 1:06 PM, Simon Goldschmidt wrote:
>>> On Tue, Jan 8, 2019 at 12:20 PM Marek Vasut wrote:
On 1/8/19 7:41 AM, Simon Goldschmidt wrote:
> On Mon, Jan 7, 2019 at 11:58 PM
On Tue, Jan 8, 2019 at 1:08 PM Marek Vasut wrote:
>
> On 1/8/19 1:06 PM, Simon Goldschmidt wrote:
> > On Tue, Jan 8, 2019 at 12:20 PM Marek Vasut wrote:
> >>
> >> On 1/8/19 7:41 AM, Simon Goldschmidt wrote:
> >>> On Mon, Jan 7, 2019 at 11:58 PM Marek Vasut wrote:
>
> On 1/7/19 10:01
On 1/8/19 1:06 PM, Simon Goldschmidt wrote:
> On Tue, Jan 8, 2019 at 12:20 PM Marek Vasut wrote:
>>
>> On 1/8/19 7:41 AM, Simon Goldschmidt wrote:
>>> On Mon, Jan 7, 2019 at 11:58 PM Marek Vasut wrote:
On 1/7/19 10:01 PM, Simon Goldschmidt wrote:
> Am 07.01.2019 um 21:47 schrieb
On Tue, Jan 8, 2019 at 12:20 PM Marek Vasut wrote:
>
> On 1/8/19 7:41 AM, Simon Goldschmidt wrote:
> > On Mon, Jan 7, 2019 at 11:58 PM Marek Vasut wrote:
> >>
> >> On 1/7/19 10:01 PM, Simon Goldschmidt wrote:
> >>> Am 07.01.2019 um 21:47 schrieb Marek Vasut:
> On 1/7/19 9:33 PM, Simon
On 1/8/19 7:41 AM, Simon Goldschmidt wrote:
> On Mon, Jan 7, 2019 at 11:58 PM Marek Vasut wrote:
>>
>> On 1/7/19 10:01 PM, Simon Goldschmidt wrote:
>>> Am 07.01.2019 um 21:47 schrieb Marek Vasut:
On 1/7/19 9:33 PM, Simon Goldschmidt wrote:
> Am 07.01.2019 um 21:25 schrieb Marek Vasut:
On Mon, Jan 7, 2019 at 11:58 PM Marek Vasut wrote:
>
> On 1/7/19 10:01 PM, Simon Goldschmidt wrote:
> > Am 07.01.2019 um 21:47 schrieb Marek Vasut:
> >> On 1/7/19 9:33 PM, Simon Goldschmidt wrote:
> >>> Am 07.01.2019 um 21:25 schrieb Marek Vasut:
> On 1/7/19 9:24 PM, Simon Goldschmidt wrote:
On 1/7/19 10:01 PM, Simon Goldschmidt wrote:
> Am 07.01.2019 um 21:47 schrieb Marek Vasut:
>> On 1/7/19 9:33 PM, Simon Goldschmidt wrote:
>>> Am 07.01.2019 um 21:25 schrieb Marek Vasut:
On 1/7/19 9:24 PM, Simon Goldschmidt wrote:
> Am 07.01.2019 um 21:19 schrieb Marek Vasut:
>> On
Am 07.01.2019 um 21:47 schrieb Marek Vasut:
On 1/7/19 9:33 PM, Simon Goldschmidt wrote:
Am 07.01.2019 um 21:25 schrieb Marek Vasut:
On 1/7/19 9:24 PM, Simon Goldschmidt wrote:
Am 07.01.2019 um 21:19 schrieb Marek Vasut:
On 1/7/19 8:36 PM, Simon Goldschmidt wrote:
When debug UART is enabled
On 1/7/19 9:33 PM, Simon Goldschmidt wrote:
> Am 07.01.2019 um 21:25 schrieb Marek Vasut:
>> On 1/7/19 9:24 PM, Simon Goldschmidt wrote:
>>> Am 07.01.2019 um 21:19 schrieb Marek Vasut:
On 1/7/19 8:36 PM, Simon Goldschmidt wrote:
> When debug UART is enabled on socfpga_gen5, the debug uart
Am 07.01.2019 um 21:25 schrieb Marek Vasut:
On 1/7/19 9:24 PM, Simon Goldschmidt wrote:
Am 07.01.2019 um 21:19 schrieb Marek Vasut:
On 1/7/19 8:36 PM, Simon Goldschmidt wrote:
When debug UART is enabled on socfpga_gen5, the debug uart driver hangs
in an endless loop because
On 1/7/19 9:24 PM, Simon Goldschmidt wrote:
> Am 07.01.2019 um 21:19 schrieb Marek Vasut:
>> On 1/7/19 8:36 PM, Simon Goldschmidt wrote:
>>> When debug UART is enabled on socfpga_gen5, the debug uart driver hangs
>>> in an endless loop because 'socfpga_bridges_reset' calls printf before
>>> the
Am 07.01.2019 um 21:19 schrieb Marek Vasut:
On 1/7/19 8:36 PM, Simon Goldschmidt wrote:
When debug UART is enabled on socfpga_gen5, the debug uart driver hangs
in an endless loop because 'socfpga_bridges_reset' calls printf before
the debug UART is initialized.
After the generic fix for this
On 1/7/19 8:36 PM, Simon Goldschmidt wrote:
> When debug UART is enabled on socfpga_gen5, the debug uart driver hangs
> in an endless loop because 'socfpga_bridges_reset' calls printf before
> the debug UART is initialized.
>
> After the generic fix for this in the UART driver did not work due to
When debug UART is enabled on socfpga_gen5, the debug uart driver hangs
in an endless loop because 'socfpga_bridges_reset' calls printf before
the debug UART is initialized.
After the generic fix for this in the UART driver did not work due to
portability issues, let's just drop this printf
17 matches
Mail list logo