Hi Tomas,
On Sun, Aug 19, 2012 at 11:21 PM, Tomas Hlavacek wrote:
> Hello Graeme!
>
> On Fri, Aug 17, 2012 at 3:15 AM, Graeme Russ wrote:
>> dm_malloc(bytes, driver *)
>> |
>> +-> early_malloc(bytes, reloc_helper *) /* Pre-Relocation */
>> | |
>> | +->register_helper(reloc_helpe
Hello Graeme!
On Fri, Aug 17, 2012 at 3:15 AM, Graeme Russ wrote:
> dm_malloc(bytes, driver *)
> |
> +-> early_malloc(bytes, reloc_helper *) /* Pre-Relocation */
> | |
> | +->register_helper(reloc_helper *)
> | |
> | +->pre_reloc_malloc(size_t bytes)
> |
> +-> mal
Hi Marek,
On Fri, Aug 17, 2012 at 10:34 AM, Marek Vasut wrote:
> Dear Graeme Russ,
>
>> Hi Marek,
>>
>> On Fri, Aug 17, 2012 at 9:32 AM, Marek Vasut wrote:
>> > Dear Graeme Russ,
>> >
>> >> >> Hmm, I hadn't thought of that
>> >> >
>> >> > So, we're back to square 1 ?
>> >>
>> >> Nope - just a sl
Dear Graeme Russ,
> Hi Marek,
>
> On Fri, Aug 17, 2012 at 9:32 AM, Marek Vasut wrote:
> > Dear Graeme Russ,
> >
> >> >> Hmm, I hadn't thought of that
> >> >
> >> > So, we're back to square 1 ?
> >>
> >> Nope - just a slight tweak is all
> >
> > What tweak ?
>
> Didn't you read the rest of m
Hi Marek,
On Fri, Aug 17, 2012 at 9:32 AM, Marek Vasut wrote:
> Dear Graeme Russ,
>
>> >> Hmm, I hadn't thought of that
>> >
>> > So, we're back to square 1 ?
>>
>> Nope - just a slight tweak is all
>
> What tweak ?
Didn't you read the rest of my email?
Regards,
Graeme
___
Dear Graeme Russ,
> Hi Marek,
>
> On Fri, Aug 17, 2012 at 12:50 AM, Marek Vasut wrote:
> > Dear Graeme Russ,
> >
> > [...]
> >
> >> >> 2) We can pass a pointer to a driver_core struct (or whatever struct
> >> >> it
> >> >>
> >> >> is that holds the 'reloc' helper function pointer). We
Hi Marek,
On Fri, Aug 17, 2012 at 12:52 AM, Marek Vasut wrote:
> Dear Graeme Russ,
>
[snip]
>> When you start throwing around "discontigmem", "sparsemem" and "nifty
>> memory-management/model features" you are talking architecture specifics
>
> In uboot, not so much ... in uboot it'd be just a
Hi Marek,
On Fri, Aug 17, 2012 at 12:50 AM, Marek Vasut wrote:
> Dear Graeme Russ,
>
> [...]
>
>> >> 2) We can pass a pointer to a driver_core struct (or whatever struct it
>> >>
>> >> is that holds the 'reloc' helper function pointer). We can't pick up
>> >> misuse at compile time, but
Dear Graeme Russ,
> Hi Marek,
>
> On 08/15/2012 12:00 AM, Marek Vasut wrote:
> > Dear Graeme Russ,
> >
> >> Hi Marek,
> >>
> >> On Tue, Aug 14, 2012 at 10:37 PM, Marek Vasut wrote:
> >>> Dear Tomas Hlavacek,
> >>>
> Hello Marek,
>
> On Sun, Aug 12, 2012 at 1:16 AM, Marek Vasut
Dear Graeme Russ,
[...]
> >> 2) We can pass a pointer to a driver_core struct (or whatever struct it
> >>
> >> is that holds the 'reloc' helper function pointer). We can't pick up
> >> misuse at compile time, but dm_malloc() can print a meaningful
> >> message if it is called pre-r
Hi Tomas,
On 08/15/2012 10:00 PM, Tomas Hlavacek wrote:
> On Tue, Aug 14, 2012 at 3:54 PM, Graeme Russ wrote:
>
>>> dm_malloc you mean? I'm not happy about it, maybe Graeme can pour in some
>>> crazy
>>> juice in our direction again?
>>
>> I don't like the idea of dm_malloc() either, but it may
Hi Marek,
On 08/15/2012 09:56 AM, Marek Vasut wrote:
> Dear Graeme Russ,
>
> [...]
>
>>
>> Third path is dm_malloc() - Although ugly, it has a few nicities...
>
> Thinking about dm_malloc() ... if it's entirely different, the semantics can
> be
> adjusted too ... say to "int dm_malloc(void **
Hi Marek,
On 08/15/2012 12:00 AM, Marek Vasut wrote:
> Dear Graeme Russ,
>
>> Hi Marek,
>>
>> On Tue, Aug 14, 2012 at 10:37 PM, Marek Vasut wrote:
>>> Dear Tomas Hlavacek,
>>>
Hello Marek,
On Sun, Aug 12, 2012 at 1:16 AM, Marek Vasut wrote:
> So ... we should aim for firing u
On Tue, Aug 14, 2012 at 3:54 PM, Graeme Russ wrote:
>> dm_malloc you mean? I'm not happy about it, maybe Graeme can pour in some
>> crazy
>> juice in our direction again?
>
> I don't like the idea of dm_malloc() either, but it may be the only way to
> get this past Wolfgang in the initial pass..
Dear Graeme Russ,
[...]
>
> Third path is dm_malloc() - Although ugly, it has a few nicities...
Thinking about dm_malloc() ... if it's entirely different, the semantics can be
adjusted too ... say to "int dm_malloc(void **ptr, size_t size);":
- return int: error code
- **ptr: pointer to alloc
Dear Albert ARIBAUD,
> Hi Marek,
>
> On Tue, 14 Aug 2012 14:37:29 +0200, Marek Vasut wrote:
> > Dear Tomas Hlavacek,
> >
> > > Hello Marek,
> > >
> > > On Sun, Aug 12, 2012 at 1:16 AM, Marek Vasut wrote:
> > > > So ... we should aim for firing up the real mallocator as soon as
> > > > possibl
Dear Graeme Russ,
> Hi Marek,
>
> On Tue, Aug 14, 2012 at 10:37 PM, Marek Vasut wrote:
> > Dear Tomas Hlavacek,
> >
> >> Hello Marek,
> >>
> >> On Sun, Aug 12, 2012 at 1:16 AM, Marek Vasut wrote:
> >> > So ... we should aim for firing up the real mallocator as soon as
> >> > possible and mayb
Hi Marek,
On Tue, Aug 14, 2012 at 10:37 PM, Marek Vasut wrote:
> Dear Tomas Hlavacek,
>
>> Hello Marek,
>>
>> On Sun, Aug 12, 2012 at 1:16 AM, Marek Vasut wrote:
>> > So ... we should aim for firing up the real mallocator as soon as
>> > possible and maybe implement discontigmem (sparsemem) into
Hi Marek,
On Tue, 14 Aug 2012 14:37:29 +0200, Marek Vasut wrote:
> Dear Tomas Hlavacek,
>
> > Hello Marek,
> >
> > On Sun, Aug 12, 2012 at 1:16 AM, Marek Vasut wrote:
> > > So ... we should aim for firing up the real mallocator as soon as
> > > possible and maybe implement discontigmem (sparse
Dear Tomas Hlavacek,
> Hello Marek,
>
> On Sun, Aug 12, 2012 at 1:16 AM, Marek Vasut wrote:
> > So ... we should aim for firing up the real mallocator as soon as
> > possible and maybe implement discontigmem (sparsemem) into it, so we
> > don't have to bother with relocating pointers maybe?
> >
Hello Marek,
On Sun, Aug 12, 2012 at 1:16 AM, Marek Vasut wrote:
>
> So ... we should aim for firing up the real mallocator as soon as possible and
> maybe implement discontigmem (sparsemem) into it, so we don't have to bother
> with relocating pointers maybe?
>
> The only problem I see is platfo
Dear Wolfgang Denk,
> Dear Graeme Russ,
>
> In message
you wrote:
> > While the need for early malloc() came about from the driver model and
> > the desire to make drivers usable before relocation, I think we can all
> > agree that its scope may well not be limited to use by drivers. A few
>
>
Dear Graeme Russ,
In message
you wrote:
>
> While the need for early malloc() came about from the driver model and
> the desire to make drivers usable before relocation, I think we can all
> agree that its scope may well not be limited to use by drivers. A few
> examples I can think of the top
Hi All,
While the need for early malloc() came about from the driver model and
the desire to make drivers usable before relocation, I think we can all
agree that its scope may well not be limited to use by drivers. A few
examples I can think of the top of my head include:
- pre-console buffer
24 matches
Mail list logo
