=?gb18030?B?u9i4tKO6ILvYuLSjuiC72Li0o7ogS1ZNIFN1cHBvcnQ/?=

[=?gb18030?B?eGl1emhp?= <1450335857@qq.com>]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb18030", Size: 10011 bytes --]

Hi Eddie,
   I tested the new update source of video-dev on AST2400 and AST2500. It works on AST2500.
 On AST2400£¬the vncviewer can connect vncserver  sucessful, but its window was blank,  not shown any information of the host screen . 
Would you like to give me some advice or instruments on how to    debug this issue? 
Hi,

There are some differences with the video engine between the AST2400 and 
AST2500 that I haven't addressed yet, so probably the driver is not 
working correctly on the AST2400 yet. Some registers have different bit 
mapping, and things like that. Sorry about that... thanks for trying it 
out! I'll look at the changes needed for AST2400 next.

Thanks,

Eddie


On 08/01/2018 03:47 AM, xiuzhi wrote:
> Hi Eddie,
>   Now It works, but the vncviewer can not connect the BMC server 
> successful.
> When I use vncviewer connect to the BMC the error read:
> "RFB protocol error: bad desktop size 0x1"
> "RFB protocol error: unknow rect encoding 7"
> The information on BMC are :
> root@zhaoxinc:~# obmc-ikvm -v /dev/video0 -i /dev/hidg0
> frame buffer size: 3145728
> 19/07/2018 08:20:57 Listening for VNC connections on TCP port 5900
> 19/07/2018 08:20:57 Listening for VNC connections on TCP6 port 5900
>
> 19/07/2018 08:52:08 Got connection from client 192.168.120.58
> 19/07/2018 08:52:08   other clients:
> 19/07/2018 08:52:08 Normal socket connection
> 19/07/2018 08:52:08 Client Protocol Version 3.8
> 19/07/2018 08:52:08 Protocol version sent 3.8, using 3.8
> 19/07/2018 08:52:08 rfbProcessClientSecurityType: executing handler 
> for type 1
> 19/07/2018 08:52:08 rfbProcessClientSecurityType: returning 
> securityResult for client rfb version >= 3.8
> 19/07/2018 08:52:08 rfbProcessClientNormalMessage: ignoring 
> unsupported encoding type Enc(0x00000018)
> 19/07/2018 08:52:08 rfbProcessClientNormalMessage: ignoring 
> unsupported encoding type Enc(0x00000016)
> 19/07/2018 08:52:08 rfbProcessClientNormalMessage: ignoring 
> unsupported encoding type Enc(0x00000015)
> 19/07/2018 08:52:08 rfbProcessClientNormalMessage: ignoring 
> unsupported encoding type Enc(0x0000000F)
> 19/07/2018 08:52:08 rfbProcessClientNormalMessage: ignoring 
> unsupported encoding type Enc(0xFFFFFEC6)
> 19/07/2018 08:52:08 Enabling full-color cursor updates for client 
> 192.168.120.58
> 19/07/2018 08:52:08 Enabling NewFBSize protocol extension for client 
> 192.168.120.58
> 19/07/2018 08:52:08 Using ZRLE encoding for client 192.168.120.58
> 19/07/2018 08:52:08 Pixel format for client 192.168.120.58:
> 19/07/2018 08:52:08   8 bpp, depth 6
> 19/07/2018 08:52:08   true colour: max r 3 g 3 b 3, shift r 4 g 2 b 0
> 19/07/2018 08:52:08 rfbProcessClientNormalMessage: ignoring 
> unsupported encoding type Enc(0x00000018)
> 19/07/2018 08:52:08 rfbProcessClientNormalMessage: ignoring 
> unsupported encoding type Enc(0x00000016)
> 19/07/2018 08:52:08 rfbProcessClientNormalMessage: ignoring 
> unsupported encoding type Enc(0x00000015)
> 19/07/2018 08:52:08 rfbProcessClientNormalMessage: ignoring 
> unsupported encoding type Enc(0x0000000F)
> 19/07/2018 08:52:08 rfbProcessClientNormalMessage: ignoring 
> unsupported encoding type Enc(0xFFFFFEC6)
> 19/07/2018 08:52:08 Enabling full-color cursor updates for client 
> 192.168.120.58
> 19/07/2018 08:52:08 Enabling NewFBSize protocol extension for client 
> 192.168.120.58
> 19/07/2018 08:52:08 Switching from ZRLE to raw Encoding for client 
> 192.168.120.58
> 19/07/2018 08:52:08 rfbProcessClientNormalMessage: ignoring 
> unsupported encoding type Enc(0x00000018)
> 19/07/2018 08:52:08 rfbProcessClientNormalMessage: ignoring 
> unsupported encoding type Enc(0x00000016)
> 19/07/2018 08:52:08 rfbProcessClientNormalMessage: ignoring 
> unsupported encoding type Enc(0x00000015)
> 19/07/2018 08:52:08 rfbProcessClientNormalMessage: ignoring 
> unsupported encoding type Enc(0x0000000F)
> 19/07/2018 08:52:08 rfbProcessClientNormalMessage: ignoring 
> unsupported encoding type Enc(0xFFFFFEC6)
> 19/07/2018 08:52:08 Enabling full-color cursor updates for client 
> 192.168.120.58
> 19/07/2018 08:52:08 Enabling NewFBSize protocol extension for client 
> 192.168.120.58
> 19/07/2018 08:52:08 Switching from raw to ZRLE Encoding for client 
> 192.168.120.58
> 19/07/2018 08:52:08 Pixel format for client 192.168.120.58:
> 19/07/2018 08:52:08   32 bpp, depth 24, little endian
> 19/07/2018 08:52:08   true colour: max r 255 g 255 b 255, shift r 16 g 
> 8 b 0
> [ 6928.751385] aspeed-video 1e700000.video: disabling comp ready irq, 
> seq_ctrl[000500a8]
> 19/07/2018 08:52:09 rfbProcessClientNormalMessage: read: Connection 
> reset by peer
> 19/07/2018 08:52:09 Client 192.168.120.58 gone
> 19/07/2018 08:52:09 Statistics             events    Transmit/ 
> RawEquiv ( saved)
> 19/07/2018 08:52:09  FramebufferUpdate   :      3 | 0/        0 (  0.0%)
> 19/07/2018 08:52:09  tight               :      1 |     30991/ 3145740 
> ( 99.0%)
> 19/07/2018 08:52:09  raw                 :      1 |     16396/ 16396 
> (  0.0%)
> 19/07/2018 08:52:09  ZRLE                :      2 |        62/ 3932160 
> (100.0%)
> 19/07/2018 08:52:09  RichCursor          :      3 | 429/      429 (  0.0%)
> 19/07/2018 08:52:09  TOTALS              :     10 |     47878/ 7094725 
> ( 99.3%)
> 19/07/2018 08:52:09 Statistics             events    Received/ 
> RawEquiv ( saved)
> 19/07/2018 08:52:09  FramebufferUpdate   :      4 | 40/       40 (  0.0%)
> 19/07/2018 08:52:09  SetPixelFormat      :      2 | 40/       40 (  0.0%)
> 19/07/2018 08:52:09  SetEncodings        :      3 | 168/      168 (  0.0%)
> 19/07/2018 08:52:09  TOTALS              :      9 | 248/      248 (  0.0%)
>
> What wrong with it?
> BTW, vncview download from 
> https://www.realvnc.com/en/connect/download/viewer/linux/
> I also got the same error using Tightvnc viewer
> Thanks,
> xiuzhi
> Hi Eddie,
>    My bmc is AST2400, I modified the aspeed-g4.dtsi(adding gfx: 
> display@1e6e6000  and  video: video@1e700000)
>  and the aspeed-bmc-opp-xxx.dts (adding &video &vhub) .
> An error occured when I executed the following instructions:
>
> root@zhaoxinc:~# create_usbhid.sh
> root@zhaoxinc:~# obmc-ikvm -v /dev/video0 -i /dev/hidg0
> [  125.586061] aspeed-video 1e700000.video: timed out on 1st mode detect
> [  125.602732] aspeed-video 1e700000.video: Failed to start video engine
> failed to open /dev/video0: 62 Timer expired
> Need I modify drivers/media/platform/aspeed-video.c or any other files?
>
>  Thanks ,
> Xiuzhi
> On 07/31/2018 01:52 AM, xiuzhi wrote:
> > Hi Alexander ,Eddie,
> >   I merged the source from
> > https://gerrit.openbmc-project.xyz/#/c/openbmc/openbmc/+/11500/,and
> > kernel branch video-dev.
> > How to test the video kvm feature by phosphor-webui or command line?
>
> Hi,
>
> You need to make sure the video device is enabled in your device-tree
> for the machine you use... My kernel patch enabled it for our AST2500
> witherspoon system. If you're using AST2500 as well, then you just need
> something like:
>
> &video {
>      status = "okay";
>      memory-region = <&gfx_memory>;
> };
>
> And the virtual USB hub:
> &vhub {
>      status = "okay";
> };
>
> If you're not using AST2500, you'll need more changes to device-tree.
>
> Then on the BMC command line:
> create_usbhid.sh
> obmc-ikvm -v /dev/video0 -i /dev/hidg0
> And connect with any VNC client to port 0 of your BMC IP.
>
> Thanks,
> Eddie
>
> > Best,
> > xiuzhi
> >
> >
> > ------------------ ԭʼÓʼþ ------------------
> > *·¢¼þÈË:* "Alexander A. Filippov"<a.filippov@yadro.com>;
> > *·¢ËÍʱ¼ä:* 2018Äê7ÔÂ25ÈÕ(ÐÇÆÚÈý) ÏÂÎç4:56
> > *ÊÕ¼þÈË:* 
> "openbmc"<openbmc@lists.ozlabs.org>;"xiuzhi"<1450335857@qq.com>;
> > *Ö÷Ìâ:* Re: KVM Support?
> >
> > Hello everybody,
> >
> > Could you check the size of
> > 
> `build/tmp/deploy/image/<platformname>/fitImage-openbmc-phosphor-initramfs-*.bin`?
> > If it exceeds 4456448 (0x440000) bytes, this is the problem described
> > at https://github.com/openbmc/openbmc/issues/3314
> >
> >
> > In this case you should modify flash partitions layout or trying to
> > decrease kernel size.
> >
> > --
> > Alexander
> >
> > On Wed, Jul 25, 2018 at 03:48:04PM +0800, xiuzhi wrote:
> > > Hi Eddie,
> > >
> > >
> > >   I read your KVM Support email on mailinglist.
> > >
> > >
> > > I am going to port the BMC kvm to ast2400 . The u-boot can not load
> > kernel ,the error message read:
> > >
> > >
> > > ""U-Boot 2016.07 (Jul 23 2018 - 11:11:50 +0000)
> > >
> > >
> > > DRAM:  240 MiB
> > > WARNING: Caches not enabled
> > > Flash: 32 MiB
> > > *** Warning - bad CRC, using default environment
> > >
> > >
> > > In:    serial
> > > Out:   serial
> > > Err:   serial
> > > Net:   aspeednic#0
> > > Error: aspeednic#0 address not set.
> > >
> > >
> > > Hit any key to stop autoboot:  0
> > > ## Loading kernel from FIT Image at 20080000 ...
> > > Bad FIT kernel image format!
> > > ERROR: can't get kernel image!
> > > ast#
> > >
> > >
> > > I added  config options to defconfig of ast2400 as follows:
> > >
> > >
> > > CONFIG_MEDIA_SUPPORT=y
> > > CONFIG_MEDIA_CAMERA_SUPPORT=y
> > > CONFIG_MEDIA_SUPPORT=y
> > > CONFIG_MEDIA_CAMERA_SUPPORT=y
> > > # CONFIG_MEDIA_ANALOG_TV_SUPPORT is not set
> > > # CONFIG_MEDIA_DIGITAL_TV_SUPPORT is not set
> > > # CONFIG_MEDIA_RADIO_SUPPORT is not set
> > > # CONFIG_MEDIA_SDR_SUPPORT is not set
> > > # CONFIG_MEDIA_CEC_SUPPORT is not set
> > > # CONFIG_MEDIA_CONTROLLER is not set
> > > CONFIG_RATIONAL=y
> > > CONFIG_VIDEO_DEV=y
> > > CONFIG_VIDEO_V4L2=y
> > > CONFIG_V4L_PLATFORM_DRIVERS=y
> > > CONFIG_VIDEO_ASPEED=y
> > > CONFIG_MEDIA_SUBDRV_AUTOSELECT=y
> > >
> > >
> > > Need I modify the aspeed-bmc-opp-palmetto.dts and aspeed-g4.dtsi?
> > >
> > >
> > > Can you give me the file list need to modify?
> > >
> > >
> > > Thanks,
> > >
> > >
> > > xiuzhi

[-- Attachment #2: Type: text/html, Size: 13302 bytes --]