kbuild

kbuild

[Otto Wyss]

IMO kbuild makes it easy to test new framebuffer drivers by anyone. So
I've started to document the tester's part on the web
"http://linux-fvdev.sourceforge.net/index.php?page=kbuilddocs.html". Now
it would be nice if someone could create a correct Makefile for a
framebuffer (preferable radeonfb) and send it to me, so I can put it
into the linux-fbdev CVS.

I first like to put up a sample so all framebuffer drivers have about
the same structure. Afterwards any maintainer may decide if he wants to
get write access to the CVS for his driver. It doesn't necessarily need
to be the official maintainer but they have precedence.

O. Wyss

-- 
See a huge pile of work at "http://wyodesktop.sourceforge.net/"


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php

Re: kbuild

[Kronos]

Il Thu, Sep 23, 2004 at 06:48:10PM +0200, Otto Wyss ha scritto: 
> *This message was transferred with a trial version of CommuniGate(tm) Pro*
> IMO kbuild makes it easy to test new framebuffer drivers by anyone. So
> I've started to document the tester's part on the web
> "http://linux-fvdev.sourceforge.net/index.php?page=kbuilddocs.html". Now
> it would be nice if someone could create a correct Makefile for a
> framebuffer (preferable radeonfb) and send it to me, so I can put it
> into the linux-fbdev CVS.

It's very simple, a skeleton would be like that:

obj-m += myfb.o

If the object is composed by 2 or more files:

obj-m += myfb.o
myfb-objs := file1.o file2.o file3.o

Note that this will build a module regardless of what the user has in his
.config file. For drivers that has suboptions (like I2C bus for
radeonfb) you can either:
- rely on the .config from user. In this case you can just copy and
  adapt a bit the Makefile from the kernel tree. For radeonfb:

obj-m += radeonfb.o

radeonfb-y                              := radeon_base.o radeon_pm.o radeon_monitor.o radeon_accel.o
radeonfb-$(CONFIG_FB_RADEON_I2C)        += radeon_i2c.o
radeonfb-objs                           := $(radeonfb-y)

- force some options. In this case you may have to define some symbols
  manualy. Like this:

obj-m += radeonfb.o

# Force CONFIG_FB_RADEON_I2C
EXTRA_CFLAGS := -DCONFIG_FB_RADEON_I2C

radeonfb-objs   := radeon_base.o radeon_pm.o radeon_monitor.o radeon_accel.o radeon_i2c.o

Also note that some driver may need some header not present in the build
directory nor in the the standard include path. radeonfb, for example,
include "../edid.h".

HTH,
Luca
-- 
Home: http://kronoz.cjb.net
Se il  destino di un uomo  e` annegare, anneghera` anche  in un bicchier
d'acqua.
Proverbio yddish


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php

Re: kbuild

[Otto Wyss]

Kronos wrote:
> 
> It's very simple, a skeleton would be like that:
> 
It would be terrible nice if someone could work out a goood sample, test
it out and send it to me. IMO it's important for the success of
linux-fbdev but I simply don't have the time to do it myself.

O. Wyss

-- 
See a huge pile of work at "http://wyodesktop.sourceforge.net/"


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php