Re: Legacy tty1 support in pvops kernels

[Jeremy Fitzhardinge <jeremy@goop.org>]

On 05/11/2010 05:42 PM, Major Hayden wrote:
> Hey there,
>
> We have quite a few legacy environments that already have pre-built domU images that depend on /dev/sdX for block devices and /dev/tty1 for console access.  The /dev/xvdX -> /dev/sdX change is trivial:
>
> diff --git a/drivers/block/xen-blkfront.c b/drivers/block/xen-blkfront.c
> index b8578bb..9c8aaa4 100644
> --- a/drivers/block/xen-blkfront.c
> +++ b/drivers/block/xen-blkfront.c
> @@ -117,7 +117,7 @@ static DEFINE_SPINLOCK(blkif_io_lock);
> #define VDEV_IS_EXTENDED(dev) ((dev)&(EXTENDED))
> #define BLKIF_MINOR_EXT(dev) ((dev)&(~EXTENDED))
>
> -#define DEV_NAME       "xvd"   /* name in /dev */
> +#define DEV_NAME       "sd"    /* name in /dev */
>
> static int get_id_from_freelist(struct blkfront_info *info)
> {
>
> However, I'm struggling with the hvc0 -> tty1 change.  In short, I'm looking to bring up a domU that is pre-configured to use tty1 as its console.  I understand that the virtual terminal drivers and hvc drivers are different and that the OS will see them differently as it boots.  I made these adjustments in the hopes that something would work:
>
> diff --git a/drivers/char/Kconfig b/drivers/char/Kconfig
> index 6aad99e..cd2888d 100644
> --- a/drivers/char/Kconfig
> +++ b/drivers/char/Kconfig
> @@ -5,7 +5,7 @@
> menu "Character devices"
>
> config VT
> -       bool "Virtual terminal" if EMBEDDED
> +       bool "Virtual terminal"
>       depends on !S390
>       select INPUT
>       default y
>
> diff --git a/drivers/char/hvc_console.c b/drivers/char/hvc_console.c
> index a632f25..eff0900 100644
> --- a/drivers/char/hvc_console.c
> +++ b/drivers/char/hvc_console.c
> @@ -44,7 +44,7 @@
> #include "hvc_console.h"
>
> #define HVC_MAJOR      229
>   

Did you try changing the major to 4 as well?  To match /dev/ttyX?

    J