All of lore.kernel.org
 help / color / mirror / Atom feed
From: mailing@thorsten-alge.de
To: linux-newbie@vger.kernel.org
Subject: [Kein Betreff]
Date: Mon,  8 Sep 2003 14:10:51 +0200 (CEST)	[thread overview]
Message-ID: <20030908121051.D5C5510B797@basicbox1.server-home.net> (raw)

Hi,

    i've installed an Aurox Linux on my ThinkPad. I want to use my
USB - MP3-Player with it. Also 
i added the following lines into the
'/usr/src/linux/drivers/usb/storage/unusual_dev.h' :

UNUSUAL_DEV ( 0x09bc, 0x0003, 0x0000, 0x9999,
			"PONTIS",
			"SP600",
			US_SC_SCSI, US_PR_BULK, NULL,
			US_FL_START_STOP),
	
    I've tested it on a Debian-Linux with an 2.4.18 kernel and it
runs. But if i want to compile it on 
my ThinkPad whith a 2.4.22 kernel from kernel.org i got the following
error message:

In file included from usb.c:190:
	unusual_devs.h:641: `US_FL_START_STOP' undeclared here (not
in a function)
	unusual_devs.h:641: initializer element is not constant
	unusual_devs.h:641: (near initialization for
`us_unusual_dev_list[63].flags')
	unusual_devs.h:641: initializer element is not constant
	unusual_devs.h:641: (near initialization for
`us_unusual_dev_list[63]')
	usb.c:194: initializer element is not constant
	usb.c:194: (near initialization for
`us_unusual_dev_list[64]')
	usb.c:196: initializer element is not constant
	usb.c:196: (near initialization for
`us_unusual_dev_list[65]')
	...
	.
	.
	...
	usb.c:232: initializer element is not constant
	usb.c:232: (near initialization for
`us_unusual_dev_list[81]')
	usb.c:235: initializer element is not constant
	usb.c:235: (near initialization for
`us_unusual_dev_list[82]')
	make[4]: *** [usb.o] Fehler 1
	make[3]: *** [first_rule] Fehler 2
	make[2]: *** [_subdir_storage] Fehler 2
	make[1]: *** [_subdir_usb] Fehler 2
	make: *** [_dir_drivers] Fehler 2
	
    I can't understand this error message, so i can't repair it and i
can't use my MP3-Player. Any 
help or pointers on this issue would be nice for me.

Thanks 

    Thorsten


PS: Excuse for my bad english...
-- 
Thorsten Alge <mailing@thorsten-alge.de>
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" 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.linux-learn.org/faqs

             reply	other threads:[~2003-09-08 12:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-08 12:10 mailing [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-12-05 11:51 [Kein Betreff] listen
2005-01-06  8:38 (kein Betreff) Harald Mehlem
2005-03-23 14:18 manitu
2006-12-04  8:35 Christian Zehring
2009-05-24 11:35 Stefan Below
2009-07-27 14:30 [PATCH 0/7 v5] KVM: support for 1gb pages Joerg Roedel
2009-07-27 14:30 ` [PATCH 6/7] kvm/mmu: enable gbpages by increasing nr of pagesizes Joerg Roedel
2009-07-27 14:35   ` (kein Betreff) Jens Regel
2010-07-28 23:40 (unknown), Maxim Levitsky
2010-07-29  7:23 ` <kein Betreff> Christoph Bartelmus
2010-07-29  7:23   ` Christoph Bartelmus
2017-07-24 20:34 [Kein Betreff] Lars Reichardt
2017-07-25  6:50 Lars Reichardt
2017-07-26  5:59 Lars Reichardt
2017-07-26  5:59 Lars Reichardt
2021-12-07 19:45 (kein Betreff) NFS Traumatized Linux User

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=20030908121051.D5C5510B797@basicbox1.server-home.net \
    --to=mailing@thorsten-alge.de \
    --cc=linux-newbie@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.