All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: No more vcs1 and vcsa1 in 2.6.30.N
Date: Fri, 10 Jul 2009 21:42:10 -0300	[thread overview]
Message-ID: <4A57DFE2.7020309@yahoo.com.ar> (raw)
In-Reply-To: <1247271564.32205.2.camel@yio.site>

Kay Sievers wrote:
> On Fri, 2009-07-10 at 17:35 -0300, Gerardo Exequiel Pozzi wrote:
>   
>> Since upgrade my system to 2.6.30[.1]. I don't have anymore
>> /sys/devices/virtual/vc/vcs1 and /sys/devices/virtual/vc/vcs1 in
>> consequence not have anymore the corresponding char devs in /dev.
>>     
>
> Seems we missed the consoles, which are always pre-allocated, and not
> created on demand. Does this help?
>
> Thanks,
> Kay
>
> diff --git a/drivers/char/vc_screen.c b/drivers/char/vc_screen.c
> index d94d25c..c1791a6 100644
> --- a/drivers/char/vc_screen.c
> +++ b/drivers/char/vc_screen.c
> @@ -495,11 +495,15 @@ void vcs_remove_sysfs(int index)
>  
>  int __init vcs_init(void)
>  {
> +	unsigned int i;
> +
>  	if (register_chrdev(VCS_MAJOR, "vcs", &vcs_fops))
>  		panic("unable to get major %d for vcs device", VCS_MAJOR);
>  	vc_class = class_create(THIS_MODULE, "vc");
>  
>  	device_create(vc_class, NULL, MKDEV(VCS_MAJOR, 0), NULL, "vcs");
>  	device_create(vc_class, NULL, MKDEV(VCS_MAJOR, 128), NULL, "vcsa");
> +	for (i = 0; i < MIN_NR_CONSOLES; i++)
> +		vcs_make_sysfs(i);
>  	return 0;
>  }
>
>
>
>   
Yes, the problem is solved applying this patch. Thanks for the quick fix
Kay.

Good Luck!

-- 
Gerardo Exequiel Pozzi ( djgera )
http://www.djgera.com.ar
KeyID: 0x1B8C330D
Key fingerprint = 0CAA D5D4 CD85 4434 A219  76ED 39AB 221B 1B8C 330D


      reply	other threads:[~2009-07-11  0:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-10 20:35 No more vcs1 and vcsa1 in 2.6.30.N Gerardo Exequiel Pozzi
2009-07-11  0:19 ` Kay Sievers
2009-07-11  0:42   ` Gerardo Exequiel Pozzi [this message]

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=4A57DFE2.7020309@yahoo.com.ar \
    --to=vmlinuz386@yahoo.com.ar \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.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.