Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263058AbUDEUxV (ORCPT ); Mon, 5 Apr 2004 16:53:21 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263193AbUDEUxU (ORCPT ); Mon, 5 Apr 2004 16:53:20 -0400 Received: from rtlab.med.cornell.edu ([140.251.145.175]:29638 "EHLO openlab.rtlab.org") by vger.kernel.org with ESMTP id S263058AbUDEUxR (ORCPT ); Mon, 5 Apr 2004 16:53:17 -0400 Date: Mon, 5 Apr 2004 16:53:16 -0400 (EDT) From: "Calin A. Culianu" X-X-Sender: To: Subject: Stupid question re: register_cdrom() Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 853 Lines: 22 Let's say I was coding a cdrom emulator in software for kernel 2.4. I am unclear about register_cdrom(). Does register_cdrom() in cdrom.c take care of telling the kernel that my kdev_t major/minor combination in fact leads to a real driver? Or do I need to take care of that outside of regsiter_cdrom()? If not.. how do I tell the kernel data structures that my driver's major number does in fact point to a cdrom driver. Basically, I want my driver's major number to show up in /proc/devices.. This might be a stupid question, but I am not a linux kernel expert... Thanks for your patience! -Calin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/