[haiku-development] Re: determining radeon kernel needed structures
- From: marius adrian popa <mapopa@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Tue, 19 Apr 2011 16:59:21 +0300
On Tue, Apr 19, 2011 at 9:15 AM, marius adrian popa <mapopa@xxxxxxxxx> wrote:
> On Mon, Apr 18, 2011 at 12:03 AM, Urias McCullough
> <umccullough@xxxxxxxxx> wrote:
>> On Sun, Apr 17, 2011 at 12:54 PM, marius adrian popa <mapopa@xxxxxxxxx>
>> wrote:
>>> On Thu, Apr 14, 2011 at 4:38 PM, Philippe Houdoin
>>> <philippe.houdoin@xxxxxxxxx> wrote:
>>>>>> ps: i wish there was a tool that extracts the headers and structures
>>>>>> needed for one module
>>>>>
>>>>> Not sure if I recall that correctly, but I thought there was a gcc option
>>>>> that would also dump which files are included (maybe even just "-v").
>>>>
>>>> That would be the gcc -M preprocessor options set.
>>>> These options outputs a file with a make rules describing module
>>>> header(s) dependencies.
>>>>
>>>> It's often use in make-based build system to support automatic
>>>> dependencies.
>>>
>>> Thanks , what i have worked last days
>>> http://mapopa.blogspot.com/search?q=haiku
>>> i have installed haiku on kvm/qemu machine installed on it's own
>>> partitions on 3 machines (one with intel eeepc , one with radeon , one
>>> with nvidia)
>>
>> You can build the image directly to a USB stick by defining a build
>> profile of type "disk" - this will prevent you from having to specify
>> the image size up front.
>>
>> Read up on build profiles :)
>
>
> I read now about the profiles in the sample
>
> Another good news is we have simpler kms driver to start from and to
> understand :
> qemu-kvm
> http://lists.freedesktop.org/archives/dri-devel/2011-April/010396.html
>
> it's simple to debug it in the kvm/qemu
>
I have patched rc linux kernel with the above patch and seems that
is booted into the qemu/kvm machine
http://mapopa.blogspot.com/2011/04/cirrus-acceleration-on-kvmqemu.html
[ 3.316695] cirrus 0000:00:02.0: setting latency timer to 64
[ 3.350323] Console: switching to colour frame buffer device 160x64
[ 3.364548] fb0: cirrusdrmfb frame buffer device
[ 3.364551] drm: registered panic notifier
[ 3.364823] [drm] Initialized cirrus 1.0.0 20110418 for
0000:00:02.0 on minor 0
lsmod | grep kms
drm_kms_helper 27159 1 cirrus
drm 163075 2 cirrus,drm_kms_helper
i2c_core 23909 3 drm_kms_helper,i2c_piix4,drm
Even if is that simple is using a lot of the kernel api and drm
structures so is still a lot of work left to be done
but is good to test the api
cd /home/mariuz/work/linux-2.6/drivers/gpu/drm/cirrus
make cirrus
https://gist.github.com/927826
Other related posts:
