Hi,
I built 1090 with pxafb and the .ppm image displays nicely. So, it's just a
matter
of back-tracking what's changed. Sigh...
On 8/29/07, Peter Lu <plu777@...> wrote:
>
> Hi, John,
>
> Thank you for this clarification. As I mentioned, I did have the LCD
> driver running with
> vintage Gumstix rev 1090. I may revert to 1090 for sanity checking if
> needed, but
> it's a pain moving backwards at this point. And it's also not
> particularly useful to me,
> as I'm committed to 1491+ because of other features I need. I was
> considering
> running a 1090 build next to a 1491 build, to see how the hardware signals
> going
> to the LCD differ, but I'll do this reverse engineering only if/when I get
> desperate.
>
> I've diff'ed the 1090 and 1491 pxafb code and there have been significant
> changes,
> including support for different LCDs. So, it's likely that something is
> now busted
> for the acx705akm as a result. I'm going to assume that no one has 1491+
> working with the acx705akm, and will have to painstakingly go through the
> code
> to figure out what is wrong or has changed since 1090.
>
> BTW, do you know why no one uses the Sony-specified parameters for the
> acx705akm? With the current pxafb driver, using the Sony specs of 272
> dots
> by 200 lines with active low syncs, for the 240x160 display seems to work
> out fine (except for my vertical overlay problem). I suspect that a lot
> of the
> old non-standard tweaks are there to compensate for bugs/limitations of
> the
> old pxafb.
>
> Thanks for your valuable input.
>
>
>
> On 8/29/07, John Alfredo <jalfredo@...> wrote:
> >
> > Hi Peter,
> >
> >
> >
> > I'm running an older version, 1084 I believe, where the only choice was
> > framebuffer. I didn't plan to update to a newer buildroot until I bought a
> > newer 16M gumstix (my basix has only 4M RAM), so I'll have to deal with the
> > LCD issue at that time. I hope you're able to find a solution to this.
> >
> >
> >
> > Regards,
> >
> >
> >
> > John Alfredo
> >
> >
> >
> > PS: why don't you retrieve an earlier buildroot storing the newer one
> > off somewhere, verify that your wiring works on the older one, then look to
> > see what's different with respect to the LCD. That's probably what I will
> > do. I can't remember the command, however if you search the archives (use
> > GMANE) there's a command to list the comments for the various SVN versions.
> > I did this once and do remember seeing some stuff about the framebuffer and
> > various displays. Check the wiki.
> > ------------------------------
> >
> > *From:* gumstix-users-bounces@... [mailto:
> > gumstix-users-bounces@...] * On Behalf Of *Peter Lu
> > *Sent:* Wednesday, August 29, 2007 7:20 AM
> > *To:* General mailing list for gumstix users.
> > *Subject:* Re: [Gumstix-users] Sony Acx705akm LCD display
> >
> >
> >
> > Hi,
> >
> > I'm certain the display is the Sony acx705akm. I know the hardware
> > works because I have some legacy software (Gumstix 1090 vintage) that
> > managed to run the LCD properly. Unfortunately, for various reasons, I
> > can't recover the old software easily for making comparisons. I've also
> > compared the wiring of the LCD in the reference schematics by Holly Gates
> > with that of our schematics and I believe they are essentially the same.
> >
> > Of the 3 FB drivers, which are you using? I'm configured to use the
> > Samsung right now, although I'm pretty sure the ALPS one did the same
> > mis-sync'ed vertical display. It doesn't seem that with all the explicit
> > PXA register overrides, the driver mode would make a difference, but who
> > knows.
> >
> > Thanks for help.
> >
> >
> > On 8/28/07, *John Alfredo* < jalfredo@...> wrote:
> >
> > Hi Peter,
> >
> >
> >
> > The ppmv I use is essentially unchanged from the Holly Gates version
> > which you reference in your email, so I don't think that is your problem.
> > Are you in fact using the SONY ACX705AKM or some other display?
> >
> >
> >
> > John Alfredo
> >
> >
> > ------------------------------
> >
> > *From:* gumstix-users-bounces@... [mailto:
> > gumstix-users-bounces@...] * On Behalf Of *Peter Lu
> > *Sent:* Tuesday, August 28, 2007 2:13 PM
> >
> >
> > *To:* General mailing list for gumstix users.
> > *Subject:* Re: [Gumstix-users] Sony Acx705akm LCD display
> >
> >
> >
> > Hi, John,
> >
> > Thank you so much for helping. Unfortunately, your script still leaves
> > my LCD doing pretty much the same thing, with the two overlapping penguins.
> > Could you send me your ppmv.c and gumlogo.ppm? I don't think they'd
> > make much difference, but I'm at a loss as to what's wrong.
> >
> > On 8/28/07, *John Alfredo* < jalfredo@...> wrote:
> >
> > Hi Peter,
> >
> >
> >
> > Here's the /etc/init.d script I use to initialize my SONY ACX705AKM.
> > Using these values I have undistorted ppm graphics when sent to /dev/fb0 and
> > undistorted text when sent to /dev/tty0.
> >
> >
> >
> > Regards,
> >
> >
> >
> > John Alfredo
> >
> >
> > ------------------------------
> >
> > *From:* gumstix-users-bounces@... [mailto:
> > gumstix-users-bounces@...] * On Behalf Of *Peter Lu
> > *Sent:* Monday, August 27, 2007 12:58 PM
> > *To:* General mailing list for gumstix users.
> > *Subject:* Re: [Gumstix-users] Sony Acx705akm LCD display
> >
> >
> >
> > Hi,
> >
> > The sample program ppmv_sony692 is very straight-forward. All it does
> > is take each 3-consecutive bytes of the input .ppm file, representing
> > RBG
> > pixels, and pack them into 5+6+5-bit words and write them into the frame
> >
> > buffer. I verified the obvious things, like the size of the .ppm file,
> > the
> > size of the frame buffer (device), the mode of the acx705akm (works in
> > 240x160-16) and the wiring between the LCD panel to the PXA255.
> > The fact that the penguin displays decently indicates that basic
> > parameters are functional.
> >
> > Since I'm seeing 2 penguins overlapped vertically (note penguin image
> > is stored and displayed sideways rather than upright), it's likely that
> > the
> > vsync parameters are off. I've played around with the LCCR2 register,
> > but have not managed to "lock" the vsync properly. Tweaking VSW
> > (vertical sync pulse width) doesn't seem to do much and tweaking
> > LPP (lines per panel) wreaks a lot of vertical havoc without getting
> > the proper vertical lock. This exercise is like tweaking the vertical
> > hold on old TVs.
> >
> > Does anyone have suggestions as to what PXA255 LCD Controller
> > registers might be involved in getting the vertical sync right?
> > Thanks for all help.
> >
> > On 8/24/07, *Craig Hughes* < craig@...> wrote:
> >
> > On Aug 24, 2007, at 4:04 AM, Peter Lu wrote:
> >
> > > My LCD is now apparently working, after adjusting some mechanical
> > > cabling problem and deasserting SHUTDOWN. However, when I run:
> > >
> > > ppmv_sony692 sony_penguin.ppm
> > >
> > > I get three faint penguins somewhat overlapped and a flickering
> > > screen.
> > > I'm sure the intent of the app was to display only one penguin, which
> > > would probably get rid of the flickering and faintness. The
> > > documentation seems to indicate that this app is customized for the
> > > acx705akm, so I don't know what tweaks are needed. My understanding
> > > of frame buffers and LCD parameters is minimal.
> >
> > The program makes strong compiled-in assumptions about the screen
> > resolution and bits-per-pixel depth. It basically will attempt to
> > just stuff raw bits together based on these hardcoded params, and
> > then dump that bitstream into /dev/fb0. If your screen is a
> > different x-y size or uses a different bit depth than the one the
> > program encodes for, then it won't work for you unless you modify
> > those params in the code. iirc the x-y dimensions are #defined so
> > it's easy to change those, but the code basically just completely
> > assumes some bit-depth in terms of how the algorithm works -- I
> > forget if it was 8 or 16bpp. To handle, eg, 24bpp (where maybe only
> > some of those 24bpp are significant, like when the PXA FB controller
> > is in 18bpp mode) you'll need to rewrite the algorithm to align the
> > bits correctly.
> >
> > > I have tried both the Samsung and ALPS mode drivers and the LCD
> > > behaves the same way (as expected). I think I will stick with the
> > > Samsung mode as the ALPS mode doesn't seem to support
> > > screen backlighting (by a quick look at the code).
> > >
> > > I'm also looking for some app or configuration to use the acx705akm
> > > as a simple ascii text display device. Is setting it us as a virtual
> > > terminal the best bet?
> >
> > Yes, using the fbcon is the easiest way to do text on an fb-backed
> > LCD panel.
> >
> > C
> >
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems? Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > _______________________________________________
> > gumstix-users mailing list
> > gumstix-users@...
> > https://lists.sourceforge.net/lists/listinfo/gumstix-users
> >
> >
> >
> >
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems? Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > _______________________________________________
> > gumstix-users mailing list
> > gumstix-users@...
> > https://lists.sourceforge.net/lists/listinfo/gumstix-users
> >
> >
> >
> >
> >
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems? Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > _______________________________________________
> > gumstix-users mailing list
> > gumstix-users@...
> > https://lists.sourceforge.net/lists/listinfo/gumstix-users
> >
> >
> >
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems? Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > _______________________________________________
> > gumstix-users mailing list
> > gumstix-users@...
> > https://lists.sourceforge.net/lists/listinfo/gumstix-users
> >
> >
>
|