megaraid_probe_one(9)
π megaraid_probe_one(9) β like, the Kernel API Manual entry, bestie π
okay so picture this: you're deep in the kernel, it's the Kernel API Manual, and you just found megaraid_probe_one(9). this is the PCI hotplug entry point. it's not the flashiest function at the party but it is literally the door greeter for your MegaRAID adapters, and honestly? main character energy. let's get into it π
β¨ NAME β¨
megaraid_probe_one β the PCI hotplug entry point π«Ά
that's it. that's the whole name section. short king. π
β¨ SYNOPSIS β¨
int megaraid_probe_one (struct pci_dev *pdev , const struct
pci_device_id *id );
like, it takes two things and returns an int, the way that everyone in this family does. classic. πΈ
β¨ ARGUMENTS β¨
here's the tea on what you're passing in β
pdevβ handle to this controller's PCI configuration space. yep, that's this controller's, not somebody else's. don't mix them up bestie πidβ pci device id of the class of controllers. it's giving "which flavor of controller are we even talking about" vibe check. π«
β¨ DESCRIPTION β¨
okay so the whole bit: this routine should be called whenever a new adapter is detected by the PCI hotplug subsystem. π¦
that's the entire job. new adapter shows up β you call megaraid_probe_one. no cap, that's it. it's the "hiii welcome in" of the PCI hotplug world and it ate. π₯
not me emphasizing should be called β like, this is an entry point, so it's the hotplug subsystem's job to ring it up, not something you go poking at randomly in your spare time π
β¨ SEE ALSO β¨
bestie. sit down. this list is long and every single one of them is invited to the group chat π
first off, the kernel file itself lives at ./drivers/scsi/megaraid/megaraid_mbox.c β that's home base π
and then the whole squad, in order: megaraid_init(9), megaraid_exit(9), megaraid_detach_one(9), megaraid_mbox_shutdown(9), megaraid_io_attach(9), megaraid_io_detach(9), megaraid_init_mbox(9), megaraid_fini_mbox(9), megaraid_alloc_cmd_packets(9), megaraid_free_cmd_packets(9), megaraid_mbox_setup_dma_pools(9), megaraid_mbox_teardown_dma_pools(9), megaraid_alloc_scb(9), megaraid_dealloc_scb(9), megaraid_mbox_mksgl(9), mbox_post_cmd(9), megaraid_queue_command_lck(9), megaraid_mbox_build_cmd(9), megaraid_mbox_runpendq(9), megaraid_mbox_prepare_pthru(9), megaraid_mbox_prepare_epthru(9), megaraid_ack_sequence(9), megaraid_isr(9), megaraid_mbox_dpc(9), megaraid_abort_handler(9), megaraid_reset_handler(9), mbox_post_sync_cmd(9), mbox_post_sync_cmd_fast(9), megaraid_busywait_mbox(9), megaraid_mbox_product_info(9), megaraid_mbox_extended_cdb(9), megaraid_mbox_support_ha(9), megaraid_mbox_support_random_del(9), megaraid_mbox_get_max_sg(9), megaraid_mbox_enum_raid_scsi(9), megaraid_mbox_flush_cache(9), megaraid_mbox_fire_sync_cmd(9), megaraid_mbox_display_scb(9), megaraid_mbox_setup_device_map(9), megaraid_cmm_register(9), megaraid_cmm_unregister(9), megaraid_mbox_mm_handler(9), megaraid_mbox_mm_command(9), megaraid_mbox_mm_done(9), gather_hbainfo(9), megaraid_sysfs_alloc_resources(9), megaraid_sysfs_free_resources(9), megaraid_sysfs_get_ldmap_done(9), megaraid_sysfs_get_ldmap_timeout(9), megaraid_sysfs_get_ldmap(9), megaraid_mbox_app_hndl_show(9), megaraid_mbox_ld_show(9).
yep. all of them. no skips, no "etc.", we don't do that here π 52 references and we're respecting every single one. iykyk. π
so yeah, that's the page π probe in, get your adapter, call it when hotplug says so, and go read the other fifty-one functions when you're done being obsessed with this one. mwah π
this cutie was brought to you by the source path ./drivers/scsi/megaraid, dated October 2026 β like, she's stamped and everything. periodt. π
β¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms