On Fri, Aug 7, 2015 at 5:33 AM, QIAO YANG wrote:
>
>> On Aug 7, 2015, at 10:45 AM, Pavel Pisa wrote:
>>
>> Hello Qiao Ynag,
>>
>> I am in a hurry now.
>>
>> On Friday 07 of August 2015 00:52:43 QIAO YANG wrote:
You have the MMU part right. You know where VC memory starts.
You round it d
> On Aug 7, 2015, at 10:45 AM, Pavel Pisa wrote:
>
> Hello Qiao Ynag,
>
> I am in a hurry now.
>
> On Friday 07 of August 2015 00:52:43 QIAO YANG wrote:
>>> You have the MMU part right. You know where VC memory starts.
>>> You round it down to 1MB range (because that is step size which
>>> ARM
Hello Qiao Ynag,
I am in a hurry now.
On Friday 07 of August 2015 00:52:43 QIAO YANG wrote:
> > You have the MMU part right. You know where VC memory starts.
> > You round it down to 1MB range (because that is step size which
> > ARM MMU provides in the actual RTEMS setup). Then you need to
> > l
Hi Pisa Pavel,
On Aug 03, 2015, at 11:43 AM, Pavel Pisa wrote:
Hello Qiao Yang,
On Monday 03 of August 2015 22:06:31 QIAO YANG wrote:
On Aug 03, 2015, at 08:34 AM, QIAO YANG wrote:
> On Jul 29, 2015, at 02:03 PM, Chris Johns wrote:
>> On 29/07/2015 8:04 pm, Sebastian Huber wrote:
>>> A cus
Hello Qiao Yang,
On Monday 03 of August 2015 22:06:31 QIAO YANG wrote:
> On Aug 03, 2015, at 08:34 AM, QIAO YANG wrote:
> > On Jul 29, 2015, at 02:03 PM, Chris Johns wrote:
> >> On 29/07/2015 8:04 pm, Sebastian Huber wrote:
> >>> A custom workspace initialization can be done via
> >>> bsp_work_a
On Aug 03, 2015, at 08:34 AM, QIAO YANG wrote:
On Jul 29, 2015, at 02:03 PM, Chris Johns wrote:
On 29/07/2015 8:04 pm, Sebastian Huber wrote:
A custom workspace initialization can be done via
bsp_work_area_initialize().
On the zynq the ethernet driver from Ric (SLAC) for the in tree
(
On Jul 29, 2015, at 02:03 PM, Chris Johns wrote:
On 29/07/2015 8:04 pm, Sebastian Huber wrote:
A custom workspace initialization can be done via
bsp_work_area_initialize().
On the zynq the ethernet driver from Ric (SLAC) for the in tree
(existing) IP stack there is:
uint8_t* start;
size_t
On 29/07/2015 8:04 pm, Sebastian Huber wrote:
>
> A custom workspace initialization can be done via
> bsp_work_area_initialize().
>
On the zynq the ethernet driver from Ric (SLAC) for the in tree
(existing) IP stack there is:
uint8_t* start;
size_tsize = 0x10;
uintptr_t boundary =
On 29/07/15 10:17, Pavel Pisa wrote:
Hello Sebastian,
On Wednesday 29 of July 2015 09:06:47 Sebastian Huber wrote:
On 28/07/15 02:31, Pavel Pisa wrote:
I think it's much closer to what we expected. you may checkout my
github and my dropbox.
https://github.com/yangqiao/rtems/tree/framebuffe
Hello Sebastian,
On Wednesday 29 of July 2015 09:06:47 Sebastian Huber wrote:
> On 28/07/15 02:31, Pavel Pisa wrote:
> >> >I think it's much closer to what we expected. you may checkout my
> >> > github and my dropbox.
> >> >https://github.com/yangqiao/rtems/tree/framebuffer
> >> >https://www.dr
On 28/07/15 02:31, Pavel Pisa wrote:
>I think it's much closer to what we expected. you may checkout my github
>and my dropbox.
>https://github.com/yangqiao/rtems/tree/framebuffer
>https://www.dropbox.com/sh/95bu6skofkmrlvc/AABXjwvvFhQScJdo_rwj12V6a?dl=0
>
>The commits log is messy, I'll rebase
Hello Qiao Yang,
On Saturday 25 of July 2015 14:53:35 QIAO YANG wrote:
> Hi Pavel Pisa,
>
> I've added the auto-configuration for fb section in mmu table.
> I reserve a section at the end of mmu table, make the table non-const to
> avoid errors, allocate fb before mmu initialization and fill in th
Hi Pavel Pisa,
I've added the auto-configuration for fb section in mmu table.
I reserve a section at the end of mmu table, make the table non-const to avoid
errors, allocate fb before mmu initialization and fill in the table with the
right parameters.
As far as I've tested, I've found that the
13 matches
Mail list logo
