On 03/20/2016 12:06 AM, Stephen Warren wrote:
On 03/15/2016 08:36 PM, Stephen Warren wrote:
On 03/13/2016 07:16 PM, Eric Anholt wrote:
For Raspberry Pi, we had the input clock rate to the pl011 fixed in
the rpi.c file, but it may be changed by firmware due to user changes
to config.txt. Since
On 03/15/2016 08:36 PM, Stephen Warren wrote:
On 03/13/2016 07:16 PM, Eric Anholt wrote:
For Raspberry Pi, we had the input clock rate to the pl011 fixed in
the rpi.c file, but it may be changed by firmware due to user changes
to config.txt. Since the firmware always sets up the uart (default
1
On 03/13/2016 07:16 PM, Eric Anholt wrote:
For Raspberry Pi, we had the input clock rate to the pl011 fixed in
the rpi.c file, but it may be changed by firmware due to user changes
to config.txt. Since the firmware always sets up the uart (default
115200 output unless the user changes it), we ca
On Sun, Mar 13, 2016 at 06:16:54PM -0700, Eric Anholt wrote:
> For Raspberry Pi, we had the input clock rate to the pl011 fixed in
> the rpi.c file, but it may be changed by firmware due to user changes
> to config.txt. Since the firmware always sets up the uart (default
> 115200 output unless th
For Raspberry Pi, we had the input clock rate to the pl011 fixed in
the rpi.c file, but it may be changed by firmware due to user changes
to config.txt. Since the firmware always sets up the uart (default
115200 output unless the user changes it), we can just skip our own
uart init to simplify the
5 matches
Mail list logo
