From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] BMP display.
Date: Mon, 17 Aug 2009 11:33:50 +0200 [thread overview]
Message-ID: <20090817093350.04205833DBD2@gemini.denx.de> (raw)
In-Reply-To: <200908171305.55605.chernigovskiy@spb.gs.ru>
Dear Tuma,
please keep the mailing list on Cc: - thanks.
In message <200908171305.55605.chernigovskiy@spb.gs.ru> you wrote:
>
> > In message <200908131326.20857.chernigovskiy@spb.gs.ru> you wrote:
> > > I have LCD drivers from TI for OMAP3 evm board. I need to include this
> > > files to my current u-boot. I have .h and .c files with some functional I
> > > need. I want to call some functions implemented in this files from
> > > main_loop (). I
> >
> > You definitely do NOT want to do that. the main_loop is the command
> > interpreter. Don't mess with that code.
>
> Okay. We'll talk about it a little bit later.
>
> > > put .h files in the "include" directory, adn .c files to the "drivers"
> > > directory. Then I include appropriate .h file in main.c, compile and get
> > > error:
> > > "/root/GS/Taimen/U-Boot-Upgrader/common/main.c:343: undefined reference
> > > to `enable_lcd_power'".
> > >
> > > What do I do wrong? How new files should be added to the project?
> >
> > You also have to make sure these files get linked, so check the parts
> > of the Makefiles that include objects into the respective libraries.
>
> I understand what you've written but what file should I check?
> Maybe we should start from question - where (in what directories) I should put
> my new files? I have some .h files and few .c.
I cannot answer this question without knowing that these files
contain. Is this board specific code? Then it should go into your own
board directory. Is it OMAP3 specific, generic stuff? Then it should
probably go into the cpu/arm_cortexa8/omap3 directory. Is it driver
code? Then it should go into some directory below drivers/ - maybe
into drivers/video/ ?
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
The high cost of living hasn't affected its popularity.
next prev parent reply other threads:[~2009-08-17 9:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 11:34 [U-Boot] Environment structure Tuma
2009-07-30 15:29 ` Detlev Zundel
2009-08-03 13:03 ` [U-Boot] BMP display Tuma
2009-08-05 14:31 ` Detlev Zundel
2009-08-06 11:48 ` Tuma
2009-08-06 15:25 ` Detlev Zundel
2009-08-13 9:26 ` Tuma
2009-08-13 9:45 ` Wolfgang Denk
[not found] ` <200908171305.55605.chernigovskiy@spb.gs.ru>
2009-08-17 9:33 ` Wolfgang Denk [this message]
2009-08-17 9:38 ` Tuma
2009-08-17 9:52 ` Wolfgang Denk
2009-08-17 11:12 ` Tuma
2009-08-17 11:51 ` Wolfgang Denk
[not found] ` <200908171631.17975.chernigovskiy@spb.gs.ru>
2009-08-17 12:38 ` Wolfgang Denk
2009-08-17 13:55 ` Tuma
2009-08-17 14:01 ` Tuma
2009-08-17 15:37 ` Premi, Sanjeev
2009-08-18 9:00 ` Tuma
2009-08-18 11:04 ` Wolfgang Denk
2009-08-17 20:31 ` Wolfgang Denk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090817093350.04205833DBD2@gemini.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox