On 06.12.19 17:18, Soeren Moch wrote:
> On 06.12.19 15:02, Tom Rini wrote:
>> On Fri, Dec 06, 2019 at 01:30:44PM +0100, Anatolij Gustschin wrote:
>>> Hi Stefano,
>>>
>>> On Fri, 6 Dec 2019 12:41:47 +0100
>>> Stefano Babic sba...@denx.de wrote:
>>> ...
I come later to the discussion - anyway
On 06.12.19 15:02, Tom Rini wrote:
> On Fri, Dec 06, 2019 at 01:30:44PM +0100, Anatolij Gustschin wrote:
>> Hi Stefano,
>>
>> On Fri, 6 Dec 2019 12:41:47 +0100
>> Stefano Babic sba...@denx.de wrote:
>> ...
>>> I come later to the discussion - anyway, I would like to search for a
>>> "pragmatic" sol
On Fri, Dec 06, 2019 at 01:30:44PM +0100, Anatolij Gustschin wrote:
> Hi Stefano,
>
> On Fri, 6 Dec 2019 12:41:47 +0100
> Stefano Babic sba...@denx.de wrote:
> ...
> > I come later to the discussion - anyway, I would like to search for a
> > "pragmatic" solution. I think we can discuss a lot about
Hi Stefano,
On Fri, 6 Dec 2019 12:41:47 +0100
Stefano Babic sba...@denx.de wrote:
...
> I come later to the discussion - anyway, I would like to search for a
> "pragmatic" solution. I think we can discuss a lot about which code flew
> in and why tbs2910 increases the size, but I do not know if thi
Hi Everybody,
On 22/11/19 11:29, Soeren Moch wrote:
>
>
> On 22.11.19 04:58, Marek Vasut wrote:
>> On 11/22/19 4:41 AM, Tom Rini wrote:
>> [...]
>>> I believe
>>> the specific changes in question that once again push this board
>>> over
>>> fall in to that grey a
On 11/22/19 4:44 PM, Tom Rini wrote:
> On Fri, Nov 22, 2019 at 04:58:29AM +0100, Marek Vasut wrote:
>> On 11/22/19 4:41 AM, Tom Rini wrote:
>> [...]
>>> I believe
>>> the specific changes in question that once again push this board
>>> over
>>> fall in to that grey
On Fri, Nov 22, 2019 at 04:58:29AM +0100, Marek Vasut wrote:
> On 11/22/19 4:41 AM, Tom Rini wrote:
> [...]
> > I believe
> > the specific changes in question that once again push this board
> > over
> > fall in to that grey area. Whatever size-trimming the board
On 11/22/19 11:29 AM, Soeren Moch wrote:
>
>
> On 22.11.19 04:58, Marek Vasut wrote:
>> On 11/22/19 4:41 AM, Tom Rini wrote:
>> [...]
>>> I believe
>>> the specific changes in question that once again push this board
>>> over
>>> fall in to that grey area. Whatev
On Fri, Nov 22, 2019 at 12:42:49PM +0100, Heinrich Schuchardt wrote:
> On 11/22/19 11:29 AM, Soeren Moch wrote:
> >
> >
> > On 22.11.19 04:58, Marek Vasut wrote:
> > > On 11/22/19 4:41 AM, Tom Rini wrote:
> > > [...]
> > > > > > > > > > > > I believe
> > > > > > > > > > > > the specific changes i
On 11/22/19 11:29 AM, Soeren Moch wrote:
On 22.11.19 04:58, Marek Vasut wrote:
On 11/22/19 4:41 AM, Tom Rini wrote:
[...]
I believe
the specific changes in question that once again push this board over
fall in to that grey area. Whatever size-trimming the board maintainer
is fine with next i
On 22.11.19 04:58, Marek Vasut wrote:
> On 11/22/19 4:41 AM, Tom Rini wrote:
> [...]
>> I believe
>> the specific changes in question that once again push this board over
>> fall in to that grey area. Whatever size-trimming the board
>> maintainer
>> is f
On 11/22/19 4:41 AM, Tom Rini wrote:
[...]
> I believe
> the specific changes in question that once again push this board over
> fall in to that grey area. Whatever size-trimming the board
> maintainer
> is fine with next is fine with me, but needs to get a
On Fri, Nov 22, 2019 at 03:56:14AM +0100, Marek Vasut wrote:
> On 11/22/19 3:53 AM, Tom Rini wrote:
> > On Fri, Nov 22, 2019 at 02:38:51AM +0100, Marek Vasut wrote:
> >> On 11/22/19 2:30 AM, Tom Rini wrote:
> >>> On Fri, Nov 22, 2019 at 02:27:16AM +0100, Marek Vasut wrote:
> On 11/22/19 1:32 A
On 11/22/19 3:53 AM, Tom Rini wrote:
> On Fri, Nov 22, 2019 at 02:38:51AM +0100, Marek Vasut wrote:
>> On 11/22/19 2:30 AM, Tom Rini wrote:
>>> On Fri, Nov 22, 2019 at 02:27:16AM +0100, Marek Vasut wrote:
On 11/22/19 1:32 AM, Tom Rini wrote:
> On Fri, Nov 22, 2019 at 01:23:56AM +0100, Mare
On Fri, Nov 22, 2019 at 02:38:51AM +0100, Marek Vasut wrote:
> On 11/22/19 2:30 AM, Tom Rini wrote:
> > On Fri, Nov 22, 2019 at 02:27:16AM +0100, Marek Vasut wrote:
> >> On 11/22/19 1:32 AM, Tom Rini wrote:
> >>> On Fri, Nov 22, 2019 at 01:23:56AM +0100, Marek Vasut wrote:
> On 11/21/19 11:45
On 11/22/19 2:30 AM, Tom Rini wrote:
> On Fri, Nov 22, 2019 at 02:27:16AM +0100, Marek Vasut wrote:
>> On 11/22/19 1:32 AM, Tom Rini wrote:
>>> On Fri, Nov 22, 2019 at 01:23:56AM +0100, Marek Vasut wrote:
On 11/21/19 11:45 PM, Tom Rini wrote:
> On Thu, Nov 21, 2019 at 11:01:43PM +0100, Mar
On Fri, Nov 22, 2019 at 02:27:16AM +0100, Marek Vasut wrote:
> On 11/22/19 1:32 AM, Tom Rini wrote:
> > On Fri, Nov 22, 2019 at 01:23:56AM +0100, Marek Vasut wrote:
> >> On 11/21/19 11:45 PM, Tom Rini wrote:
> >>> On Thu, Nov 21, 2019 at 11:01:43PM +0100, Marek Vasut wrote:
> On 11/21/19 10:59
On 11/22/19 1:32 AM, Tom Rini wrote:
> On Fri, Nov 22, 2019 at 01:23:56AM +0100, Marek Vasut wrote:
>> On 11/21/19 11:45 PM, Tom Rini wrote:
>>> On Thu, Nov 21, 2019 at 11:01:43PM +0100, Marek Vasut wrote:
On 11/21/19 10:59 PM, Heinrich Schuchardt wrote:
> On 11/21/19 9:12 PM, Tom Rini wro
On Fri, Nov 22, 2019 at 01:23:56AM +0100, Marek Vasut wrote:
> On 11/21/19 11:45 PM, Tom Rini wrote:
> > On Thu, Nov 21, 2019 at 11:01:43PM +0100, Marek Vasut wrote:
> >> On 11/21/19 10:59 PM, Heinrich Schuchardt wrote:
> >>> On 11/21/19 9:12 PM, Tom Rini wrote:
> On Thu, Nov 21, 2019 at 09:09
On 11/21/19 11:45 PM, Tom Rini wrote:
> On Thu, Nov 21, 2019 at 11:01:43PM +0100, Marek Vasut wrote:
>> On 11/21/19 10:59 PM, Heinrich Schuchardt wrote:
>>> On 11/21/19 9:12 PM, Tom Rini wrote:
On Thu, Nov 21, 2019 at 09:09:29PM +0100, Heinrich Schuchardt wrote:
> Hello Soeren,
>
>
On Thu, Nov 21, 2019 at 11:01:43PM +0100, Marek Vasut wrote:
> On 11/21/19 10:59 PM, Heinrich Schuchardt wrote:
> > On 11/21/19 9:12 PM, Tom Rini wrote:
> >> On Thu, Nov 21, 2019 at 09:09:29PM +0100, Heinrich Schuchardt wrote:
> >>> Hello Soeren,
> >>>
> >>> when trying to add support for function
On 11/21/19 10:59 PM, Heinrich Schuchardt wrote:
> On 11/21/19 9:12 PM, Tom Rini wrote:
>> On Thu, Nov 21, 2019 at 09:09:29PM +0100, Heinrich Schuchardt wrote:
>>> Hello Soeren,
>>>
>>> when trying to add support for function key support in the USB keyboard
>>> driver u-boot.imx for the TBS2910 sur
On 11/21/19 9:12 PM, Tom Rini wrote:
On Thu, Nov 21, 2019 at 09:09:29PM +0100, Heinrich Schuchardt wrote:
Hello Soeren,
when trying to add support for function key support in the USB keyboard
driver u-boot.imx for the TBS2910 surpassed the maximum size for u-boot.imx.
https://travis-ci.org/mare
On Thu, Nov 21, 2019 at 09:09:29PM +0100, Heinrich Schuchardt wrote:
> Hello Soeren,
>
> when trying to add support for function key support in the USB keyboard
> driver u-boot.imx for the TBS2910 surpassed the maximum size for u-boot.imx.
> https://travis-ci.org/marex/u-boot-usb/builds/614059004
Hello Soeren,
when trying to add support for function key support in the USB keyboard
driver u-boot.imx for the TBS2910 surpassed the maximum size for u-boot.imx.
https://travis-ci.org/marex/u-boot-usb/builds/614059004
Do you remember why on the TBS2910 board this size is limited to
0x5fc00? Oth
25 matches
Mail list logo