[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-discuss] quick pointer on adding a new chardev
From: |
Peter Maydell |
Subject: |
Re: [Qemu-discuss] quick pointer on adding a new chardev |
Date: |
Fri, 17 Feb 2017 17:17:38 +0000 |
On 17 February 2017 at 16:49, Herb Peyerl <address@hidden> wrote:
>> On Feb 17, 2017, at 9:36 AM, Peter Maydell <address@hidden> wrote:
>>>> qemu-system-aarch64: Option ‘-device myfoo’ cannot be handled by this
>>>> machine
>>
>> This is saying "I don't know about this device at all", and
>> doesn't have anything to do with chardevs. I would
>> start by checking that your code is really being built
>> (ie you have the makefile syntax right and have specified
>> in the right default-configs/ file that it should be
>> built for this target architecture, and that you have
>> the right syntax to register the device (the type_init
>> macro and associated boilerplate).
>
> My device is in there. I can insmod my driver on the guest and
> I see my device registers being read/written do.
If your device is already present then you don't want to
try to use -device (which would be attempting to add
a second instance of it to the system).
thanks
-- PMM
- [Qemu-discuss] quick pointer on adding a new chardev, Herb Peyerl, 2017/02/17
- Re: [Qemu-discuss] quick pointer on adding a new chardev, Peter Maydell, 2017/02/17
- Re: [Qemu-discuss] quick pointer on adding a new chardev, Herb Peyerl, 2017/02/17
- Re: [Qemu-discuss] quick pointer on adding a new chardev,
Peter Maydell <=
- Re: [Qemu-discuss] quick pointer on adding a new chardev, Herb Peyerl, 2017/02/17
- Re: [Qemu-discuss] quick pointer on adding a new chardev, Peter Maydell, 2017/02/17
- Re: [Qemu-discuss] quick pointer on adding a new chardev, Herb Peyerl, 2017/02/20
- Re: [Qemu-discuss] quick pointer on adding a new chardev, Peter Maydell, 2017/02/21
- Re: [Qemu-discuss] quick pointer on adding a new chardev, Herb Peyerl, 2017/02/21