All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wu Fengguang <wfg@linux.intel.com>
To: Shane W <shane-intel@csy.ca>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
	"Ma, Ling" <ling.ma@intel.com>,
	intel-gfx@lists.freedesktop.org, Takashi Iwai <tiwai@suse.de>,
	xorg@lists.freedesktop.org, "Fu, Michael" <michael.fu@intel.com>
Subject: Re: [RFC][PATCH] ELD routines and proc interface
Date: Fri, 21 Nov 2008 09:36:55 +0800	[thread overview]
Message-ID: <20081121013655.GA8992@localhost> (raw)
In-Reply-To: <20081120200606.GA4164@csy.ca>

Hi Shane,

On Thu, Nov 20, 2008 at 12:06:06PM -0800, Shane W wrote:
> Hi,
> 
> Ok, it appears to be the kernel I was using.  Going to a
> 2.6.27 kernel rather than 2.6.28-rc fixed the segfault.  So
> now I get ELD data though 5.1 PCM isn't quite there yet. 
> Here's the ELD info.

Thanks.

> HDMI intrinsic event: PD=1 ELDV=1
> detected monitor Haier TV*** at connection type HDMI
> supports coding type LPCM: channels = 2, rates = 44100
> 48000 88200 176400 192000 384000, bits =
> supports coding type LPCM: channels = 8, rates = 44100
> 48000 88200 176400 192000 384000, bits =

It reveals bugs in showing the bits field. Will fix it in a following
email.

> supports coding type AC-3: channels = 6, rates = 44100
> 48000 88200, max bitrate = 640000
> supports coding type DTS: channels = 7, rates = 44100 48000
> 88200 176400 192000, max bitrate = 1536000
> supports coding type DSD (One Bit Audio): channels = 6,
> rates = 48000

It's weird that DTS supports 7 channels while DSD supports 6.
DTS is simple the compressed form of DSD.

> set status page addr 0x08360000
> [drm:i915_getparam] *ERROR* Unknown parameter 5
> 
> shane@chintoka:~$ cat /proc/asound/Intel/eld#3
> monitor name            Haier TV***
> connection_type         HDMI
> eld_version             [0x2] CEA-861D or below
> edid_version            [0x1] CEA-861
> manufacture_id          0x4148
> product_id              0xb01
> port_id                 0x0
> support_hdcp            0
> support_ai              0
> audio_sync_delay        0
> speakers                [0x0]
> sad_count               8
> sad0_coding_type        [0x1] LPCM
> sad0_channels           2
> sad0_rates              [0x1ee0] 44100 48000 88200 176400
> 192000 384000
> sad0_bits               [0xe0000]
> sad1_coding_type        [0x1] LPCM
> sad1_channels           8
> sad1_rates              [0x1ee0] 44100 48000 88200 176400
> 192000 384000
> sad1_bits               [0xe0000]
> sad2_coding_type        [0x2] AC-3
> sad2_channels           6
> sad2_rates              [0xe0] 44100 48000 88200
> sad2_max_bitrate        640000
> sad3_coding_type        [0x7] DTS
> sad3_channels           7
> sad3_rates              [0x6e0] 44100 48000 88200 176400
> 192000
> sad3_max_bitrate        1536000
> sad4_coding_type        [0x9] DSD (One Bit Audio)
> sad4_channels           6
> sad4_rates              [0x40] 48000

> sad5_coding_type        [0x0] undefined
> sad5_channels           1
> sad5_rates              [0x0]
> sad6_coding_type        [0x0] undefined
> sad6_channels           1
> sad6_rates              [0x0]
> sad7_coding_type        [0x0] undefined
> sad7_channels           1
> sad7_rates              [0x0]

I wonder why the monitor report these zero valued SADs?

> The speakers 0 line is a bit confusing, not sure if that's

Yes it's unexpected. Do you know its real speaker numbers and
allocations? Does it provide some number of line-out ports?

> what's doing it.  I am using:
> aplay 51test.wav
> 
> which I have put here:
> http://www.csy.ca/~shane/51test.wav

I hear only "front left" and "front right" in my T61 :-)

Thanks,
Fengguang
---

> 
> Shane
> On Thu, Nov 20, 2008 at 09:02:04AM +0800, Wu Fengguang wrote:
> > Thanks Shane!
> > 
> > Ma Ling: do you have a quick fix for it?  Or shall I look into it?
> > 
> > Thank you,
> > Fengguang
> > 
> > On Wed, Nov 19, 2008 at 12:02:01PM -0800, Shane W wrote:
> > > On Wed, Nov 19, 2008 at 05:39:40PM +0800, Wu Fengguang wrote:
> > > > I managed to update the last working Xorg ELD patches to the latest
> > > > git tree, and they compile flawlessly. The attached 2 patches are for 
> > > > xf86-video-intel/ and xserver/ respectively.
> > > 
> > > They do compile but I can't get them to run.  Here's the
> > > Xorg backtrace when starting.  I'm having trouble
> > > generating a core but I'll work on getting gdb output if
> > > needed.
> > > 
> > > Backtrace:
> > > 0: /opt/gfx-test/bin/Xorg(xorg_backtrace+0x26) [0x4ebbb6]
> > > 1: /opt/gfx-test/bin/Xorg(xf86SigHandler+0x39) [0x495b49]
> > > 2: /lib/libc.so.6 [0x7f2d1648bf60]
> > > 3:
> > > /opt/gfx-test/lib/xorg/modules/drivers//intel_drv.so(gen4_render_state_cleanup+0x1c)
> > > [0x7f2d14ebab9c]
> > > 4: /opt/gfx-test/lib/xorg/modules/drivers//intel_drv.so
> > > [0x7f2d14e92dfd]
> > > 5: /opt/gfx-test/bin/Xorg(AbortDDX+0x8d) [0x4690fd]
> > > 6: /opt/gfx-test/bin/Xorg(AbortServer+0x1d) [0x4f505d]
> > > 7: /opt/gfx-test/bin/Xorg(LogVMessageVerb+0) [0x4f5700]
> > > 8:
> > > /opt/gfx-test/lib/xorg/modules/drivers//intel_drv.so(i830_bind_all_memory+0x102)
> > > [0x7f2d14e99592]
> > > 9: /opt/gfx-test/lib/xorg/modules/drivers//intel_drv.so
> > > [0x7f2d14e93ad0]
> > > 10: /opt/gfx-test/lib/xorg/modules/drivers//intel_drv.so
> > > [0x7f2d14e950f8]
> > > 11: /opt/gfx-test/bin/Xorg(AddScreen+0x1c6) [0x431086]
> > > 12: /opt/gfx-test/bin/Xorg(InitOutput+0x241) [0x469ae1]
> > > 13: /opt/gfx-test/bin/Xorg(main+0x205) [0x431795]
> > > 14: /lib/libc.so.6(__libc_start_main+0xe6) [0x7f2d164781a6]
> > > 15: /opt/gfx-test/bin/Xorg [0x430dd9]
> > > 
> > > It seems to be the xserver patch that's doing it.  When they
> > > are both unapplied, X starts fine, when the Xserver patch
> > > is applied, we segfault, when the intel is applied alone,
> > > it starts fine and when both are applied the segfault
> > > returns.
> > > 
> > > Shane

  parent reply	other threads:[~2008-11-21  1:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-13  2:21 [RFC][PATCH] ELD routines and proc interface Wu Fengguang
2008-11-13  7:26 ` Takashi Iwai
2008-11-14  1:34   ` Wu Fengguang
2008-11-14  7:25     ` Takashi Iwai
2008-11-14  7:38       ` Wu Fengguang
2008-11-14  7:43         ` Takashi Iwai
2008-11-14  7:47           ` Wu Fengguang
2008-11-14  7:50             ` Takashi Iwai
2008-11-14  8:02               ` Wu Fengguang
     [not found] ` <20081119071135.GA17733@csy.ca>
2008-11-19  7:17   ` Wu Fengguang
     [not found]     ` <20081119075545.GA19833@csy.ca>
2008-11-19  8:08       ` Wu Fengguang
2008-11-19  9:39         ` [alsa-devel] " Wu Fengguang
     [not found]           ` <20081119200201.GA23246@csy.ca>
     [not found]             ` <20081120010204.GA25454@localhost>
     [not found]               ` <20081120200606.GA4164@csy.ca>
2008-11-21  1:36                 ` Wu Fengguang [this message]
2008-11-21  1:42                   ` [PATCH] properly print ELD sample bits Wu Fengguang
2008-11-21  7:41                     ` Takashi Iwai
     [not found]                   ` <20081121014649.GA12072@csy.ca>
2008-11-21  1:59                     ` [Intel-gfx] [RFC][PATCH] ELD routines and proc interface Wu Fengguang
2008-11-21  3:41                     ` Wu Fengguang
2008-11-21  7:44                       ` Takashi Iwai
2008-11-21  7:47                         ` Wu Fengguang
     [not found] <20081113022153.GB6844@mail.ustc.edu.cn>
2008-11-13  2:36 ` Wu Fengguang

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=20081121013655.GA8992@localhost \
    --to=wfg@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ling.ma@intel.com \
    --cc=michael.fu@intel.com \
    --cc=shane-intel@csy.ca \
    --cc=tiwai@suse.de \
    --cc=xorg@lists.freedesktop.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.