public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] BMP display.
Date: Mon, 17 Aug 2009 11:52:46 +0200	[thread overview]
Message-ID: <20090817095246.48AD4833DBD2@gemini.denx.de> (raw)
In-Reply-To: <200908171338.23342.chernigovskiy@spb.gs.ru>

Dear Tuma,

In message <200908171338.23342.chernigovskiy@spb.gs.ru> you wrote:
...
> > 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/ ?
> 
> Yes, you're right - this is LCD driver (as I see it is based on some specific 
> i2c driver, so it should be included too). And not specific for the OMAP3 evm 
> board - OMAP3's display is only experimental for me now, final H/W will use 
> another LCD.

The LCD type is probably the least concern here.

> But I cannt find subdirectory "video" int "drivers". Do you mean "drivers" in 
> the root of U-Boot directory tree?

Yes, I do:

-> ls drivers/video/
Makefile         ati_radeon_fb.h  cfb_console.c  mx3fb.c     sed156x.c    videomodes.c
ati_ids.h        atmel_lcdfb.c    ct69000.c      s6e63d6.c   sm501.c      videomodes.h
ati_radeon_fb.c  bus_vcxk.c       mb862xx.c      sed13806.c  smiLynxEM.c


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
e-credibility: the non-guaranteeable likelihood that  the  electronic
data you're seeing is genuine rather than somebody's made-up crap.
- Karl Lehenbauer

  reply	other threads:[~2009-08-17  9:52 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
2009-08-17  9:38                   ` Tuma
2009-08-17  9:52                     ` Wolfgang Denk [this message]
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=20090817095246.48AD4833DBD2@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