public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Manu Abraham <manu@kromtek.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PCI driver
Date: Wed, 14 Sep 2005 21:16:34 +0200	[thread overview]
Message-ID: <43287712.3040503@gmail.com> (raw)
In-Reply-To: <4328735B.70800@kromtek.com>

Manu Abraham napsal(a):
> Jiri Slaby wrote:
> 
>> Manu Abraham napsal(a):
>>
>>> Jiri Slaby wrote:
>>>
>>>> you do NOT do this at all, because you have pdev already (the param 
>>>> of the probe function)
>>>>
>>>
>>> I rewrote the entire thing like this including the pci_remove 
>>> function too, but now it so seems that in the remove function, 
>>> pci_get_drvdata(pdev) returns NULL, and hence i get an Oops at module 
>>> removal.
>>
>>
>> Maybe because this is badly written driver.
> 
> 
> I have not written the driver, but this is my first go at it ..
> 
>>
>>> static int mantis_pci_probe(struct pci_dev *pdev, const struct 
>>> pci_device_id *mantis_pci_table)
>>> {
>>>     struct mantis_pci *mantis;
>>>     struct mantis_eeprom eeprom;
>>>     u8 revision, latency;
>>>     u8 data[2];      if (pci_enable_device(pdev)) {               
>>> dprintk(verbose, MANTIS_DEBUG, 1, "Found a mantis chip");
>>>         if ((mantis = (struct mantis_pci *) kmalloc(sizeof (struct 
>>> mantis_pci), GFP_KERNEL)) == NULL) {
>>>             dprintk(verbose, MANTIS_ERROR, 1, "Out of memory");
>>>             return -ENOMEM;
>>>         }
>>>         pci_set_master(pdev);
>>>         mantis->mantis_addr = pci_resource_start(pdev, 0);
>>>         if (!request_mem_region(pci_resource_start(pdev, 0),
>>>             pci_resource_len(pdev, 0), DRIVER_NAME)) {
>>>             kfree(mantis);
>>>             return -EBUSY;
>>>         }
>>>         pci_read_config_byte(pdev, PCI_CLASS_REVISION, &revision);
>>>         pci_read_config_byte(pdev, PCI_LATENCY_TIMER, &latency);
>>>         mantis->mantis_mmio = ioremap(mantis->mantis_addr, 0x1000);
>>>         pci_set_drvdata(pdev, mantis);       
>>
>>
>> if pci_enable_device fails, you set this?? Maybe you haven't read the 
>> doc enough.
> 
> 
> 
> I just found that, pci_enable_device() fails. So what's the way to go 
> ahead ?
JESUS.
int retval = 0;

if ((retval = pci_enable_device()))
	goto end;

...
pci_set_drvdata(pdev, mantis);
...

end:
	return retval;

not
if (pci_enable_device())
	do something
-- 
Jiri Slaby         www.fi.muni.cz/~xslaby
~\-/~      jirislaby@gmail.com      ~\-/~
241B347EC88228DE51EE A49C4A73A25004CB2A10

  reply	other threads:[~2005-09-14 19:16 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-14  9:34 PCI driver Manu Abraham
2005-09-14 10:03 ` Jiri Slaby
2005-09-14 10:02   ` Manu Abraham
2005-09-14 10:29     ` Jiri Slaby
2005-09-14 11:53       ` Manu Abraham
2005-09-14 12:22         ` Jiri Slaby
2005-09-14 12:28           ` Manu Abraham
2005-09-14 12:48           ` Manu Abraham
2005-09-14 16:16             ` Jiri Slaby
2005-09-14 17:09               ` Manu Abraham
2005-09-14 19:00                 ` Jiri Slaby
2005-09-14 19:00                   ` Manu Abraham
2005-09-14 19:16                     ` Jiri Slaby [this message]
2005-09-14 19:20                       ` Manu Abraham
2005-09-14 22:27                       ` Manu Abraham
2005-09-15  6:43                         ` Rolf Eike Beer
2005-09-15  7:45                           ` Manu Abraham
2005-09-15  8:18                             ` Rolf Eike Beer
2005-09-15  8:51                               ` Manu Abraham
2005-09-15  9:48                                 ` Rolf Eike Beer
2005-09-15 14:38                                   ` Manu Abraham
2005-09-15 14:57                                     ` Rolf Eike Beer
2005-09-15 16:59                                       ` Manu Abraham
2005-09-15 18:29                                       ` Manu Abraham
2005-09-15 10:29                                 ` Ralph Metzler
2005-09-15 10:35                                   ` Manu Abraham
2005-09-15 11:42                                   ` Manu Abraham
2005-09-15 12:08                                     ` Antonino A. Daplas
2005-09-15 12:24                                       ` Rolf Eike Beer
2005-09-15 12:32                                       ` Manu Abraham
2005-09-15 12:08                                     ` Rolf Eike Beer
2005-10-10 12:02                         ` Rolf Eike Beer
2005-10-10 12:48                           ` Manu Abraham
2005-10-10 13:25                             ` Rolf Eike Beer
2005-10-10 13:16                               ` Manu Abraham
     [not found]                             ` <3888a5cd0510100719r3fddc368oa01e07e2c42b71e@mail.gmail.com>
2005-10-10 15:00                               ` Manu Abraham
     [not found]                                 ` <3888a5cd0510100846p7f2ff70cid69a1136b9256ab6@mail.gmail.com>
2005-10-10 17:08                                   ` Manu Abraham
     [not found]                                     ` <4af2d03a0510101101n54ab0b1cvae177c3c992bf9a9@mail.gmail.com>
2005-10-10 18:28                                       ` Manu Abraham
     [not found]                             ` <3888a5cd0510100725k579809a9o374930df9988bfa3@mail.gmail.com>
2005-10-10 15:02                               ` Manu Abraham
     [not found]                           ` <4af2d03a0510100528y236a1246tfc56c08a78f072d5@mail.gmail.com>
2005-10-10 12:51                             ` Manu Abraham
  -- strict thread matches above, loose matches on Subject: below --
2010-08-28 12:17 pci driver Srinivas Mankan

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=43287712.3040503@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manu@kromtek.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox